Project Number Date
test_Tails_ISO_stable 5325 10 Dec 2024, 12:28

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 19:9.829 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:9.720
Before features/support/hooks.rb:269 0.006
Given a computer 0.200
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 30.482
When I start Tails from USB drive "old" with network unplugged 1:33.849
Then the boot device has safe access rights 3.106
And Tails is running from USB drive "old" 0.322
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.311
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:326 3.698
After features/support/hooks.rb:100 0.009
Tags: @product
2:13.451
Before features/support/hooks.rb:269 0.005
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login 1:31.470
Then Tails is running from USB drive "old" 0.349
And I create a persistent partition 30.105
And I take note of which tps features are available 2.000
Then a Tails persistence partition exists on USB drive "old" 0.855
And I shutdown Tails and wait for the computer to power off 8.479
After features/support/hooks.rb:326 0.197
After features/support/hooks.rb:100 0.008
Tags: @product
2:55.569
Before features/support/hooks.rb:269 0.005
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.096
Then Tails is running from USB drive "old" 0.390
And all tps features are active 3.886
When I write some files expected to persist 4.189
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.253
And all persistence configuration files have safe access rights 0.404
And all persistent directories from the old Tails version have safe access rights 2.502
And I take note of which tps features are available 0.554
And I shutdown Tails and wait for the computer to power off 6.422
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.685
After features/support/hooks.rb:326 0.097
After features/support/hooks.rb:100 0.009
Tags: @product
2:35.681
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.676
And I log in to a new session 20.314
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.758
And I plug USB drive "to_upgrade" 2.409
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.344
Then the running Tails is installed on USB drive "to_upgrade" 23.724
And I unplug USB drive "to_upgrade" 0.207
And I unplug USB drive "__internal" 0.246
After features/support/hooks.rb:326 2.270
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.413
Before features/support/hooks.rb:269 0.004
Given a computer 0.221
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.645
Then all tps features from the old Tails version are active 2.103
And Tails is running from USB drive "to_upgrade" 0.335
And the boot device has safe access rights 3.012
And the expected persistent files created with the old Tails version are present in the filesystem 1.407
And all persistent directories from the old Tails version have safe access rights 2.686
After features/support/hooks.rb:326 0.884
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:24.228
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.367
And no SquashFS delta is installed 0.079
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.359
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.093
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.355
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.488
When the network is plugged 0.066
And Tor is ready 22.882
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.592
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.144
Given I shutdown Tails and wait for the computer to power off 8.473
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.138
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.239
And the file system changes introduced in version 6.2~testoverlayfs are present 0.284
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.349
# 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.300
When the network is plugged 0.079
And Tor is ready 20.166
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.701
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.799
Given I shutdown Tails and wait for the computer to power off 4.353
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.254
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.901
And the file system changes introduced in version 6.3~testoverlayfs are present 0.604
And only the 6.3~testoverlayfs SquashFS delta is installed 0.087
# 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.496
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.315
When the network is plugged 0.106
And Tor is ready 19.552
Then the Upgrader considers the system as up-to-date 0.318
# 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.255
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.923
After features/support/hooks.rb:326 0.771
After features/support/hooks.rb:100 0.057
Tags: @product @automatic_upgrade
37.764
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.014
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.369
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the signing key used by the Upgrader is outdated 0.896
But a current signing key is available on our website 0.000
When the network is plugged 0.076
And Tor is ready 19.817
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.547
After features/support/hooks.rb:326 0.715
After features/support/hooks.rb:100 0.000