Project Number Date
test_Tails_ISO_stable 4964 23 Jul 2024, 16:33

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 87 0 0 0 0 87 7 0 7 20:41.385 Passed
Tags: @product
Feature Upgrading an old Tails USB installation
As a Tails user If I have an old version of Tails installed on a USB device and the USB device has a Persistent Storage I want to upgrade Tails on it and keep my Persistent Storage in the process
Tags: @product
2:26.899
Before features/support/hooks.rb:269 0.006
Given a computer 0.232
And I create a 7200 MiB disk named "old" 0.062
And I plug USB drive "old" 1.060
And I write an old version of the Tails USB image to disk "old" 31.070
When I start Tails from USB drive "old" with network unplugged 1:49.855
Then the boot device has safe access rights 3.474
And Tails is running from USB drive "old" 0.399
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.114
And udev-watchdog is monitoring the correct device 0.313
And I unplug USB drive "old" 0.251
After features/support/hooks.rb:326 3.623
After features/support/hooks.rb:100 0.011
Tags: @product
2:11.710
Before features/support/hooks.rb:269 0.006
Given a computer 0.228
And I start Tails from USB drive "old" with network unplugged and I login 1:27.693
Then Tails is running from USB drive "old" 0.449
And I create a persistent partition 31.518
And I take note of which tps features are available 2.321
Then a Tails persistence partition exists on USB drive "old" 0.830
And I shutdown Tails and wait for the computer to power off 8.669
After features/support/hooks.rb:326 0.174
After features/support/hooks.rb:100 0.009
Tags: @product
3:8.465
Before features/support/hooks.rb:269 0.005
Given a computer 0.285
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:28.186
Then Tails is running from USB drive "old" 0.355
And all tps features are active 2.041
When I write some files expected to persist 1.858
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.209
And all persistence configuration files have safe access rights 0.521
And all persistent directories from the old Tails version have safe access rights 4.075
And I take note of which tps features are available 0.496
And I shutdown Tails and wait for the computer to power off 4.093
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.341
After features/support/hooks.rb:326 0.152
After features/support/hooks.rb:100 0.012
Tags: @product
2:35.750
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.512
And I log in to a new session 22.029
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.528
And I plug USB drive "to_upgrade" 2.566
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.630
Then the running Tails is installed on USB drive "to_upgrade" 23.032
And I unplug USB drive "to_upgrade" 0.201
And I unplug USB drive "__internal" 0.250
After features/support/hooks.rb:326 2.128
After features/support/hooks.rb:100 0.000
Tags: @product
2:26.962
Before features/support/hooks.rb:269 0.006
Given a computer 0.215
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.658
Then all tps features from the old Tails version are active 2.423
And Tails is running from USB drive "to_upgrade" 0.401
And the boot device has safe access rights 4.163
And the expected persistent files created with the old Tails version are present in the filesystem 1.770
And all persistent directories from the old Tails version have safe access rights 3.329
After features/support/hooks.rb:326 1.094
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
7:12.251
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.827
And no SquashFS delta is installed 0.144
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.385
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.144
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.415
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.631
When the network is plugged 0.073
And Tor is ready 24.291
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.778
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.329
Given I shutdown Tails and wait for the computer to power off 9.594
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:23.825
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 4.487
And the file system changes introduced in version 6.2~testoverlayfs are present 0.432
And only the 6.2~testoverlayfs SquashFS delta is installed 0.156
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.434
# We'll really install Tails_amd64_6.0~testoverlayfs_to_6.3~testoverlayfs.iuk
# but we need some way to force upgrading a second time in a row
# even if only the initially installed version is considered
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.402
When the network is plugged 0.062
And Tor is ready 21.824
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.655
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.989
Given I shutdown Tails and wait for the computer to power off 4.949
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.144
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.549
And the file system changes introduced in version 6.3~testoverlayfs are present 0.563
And only the 6.3~testoverlayfs SquashFS delta is installed 0.090
# Regression test for #17425 (i.e. the Upgrader would propose
# upgrading to the version that's already running)
Given Tails system time is magically synchronized 0.359
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.318
When the network is plugged 0.072
And Tor is ready 18.653
Then the Upgrader considers the system as up-to-date 0.445
# Regression test on #8158 (i.e. the IUK's filesystem is not part of the Unsafe Browser's chroot)
And I successfully start the Unsafe Browser 15.001
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.178
After features/support/hooks.rb:326 0.817
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
39.345
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.312
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.350
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.843
But a current signing key is available on our website 0.000
When the network is plugged 0.059
And Tor is ready 20.296
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.430
After features/support/hooks.rb:326 0.797
After features/support/hooks.rb:100 0.000