Project Number Date
test_Tails_ISO_stable 5470 19 Feb 2025, 00: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:29.538 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:11.312
Before features/support/hooks.rb:269 0.003
Given a computer 0.212
And I create a 7200 MiB disk named "old" 0.040
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 30.811
When I start Tails from USB drive "old" with network unplugged 1:34.900
Then the boot device has safe access rights 3.235
And Tails is running from USB drive "old" 0.372
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.335
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:326 7.145
After features/support/hooks.rb:100 0.007
Tags: @product
2:17.471
Before features/support/hooks.rb:269 0.008
Given a computer 0.511
And I start Tails from USB drive "old" with network unplugged and I login 1:32.218
Then Tails is running from USB drive "old" 0.401
And I create a persistent partition 32.396
And I take note of which tps features are available 1.874
Then a Tails persistence partition exists on USB drive "old" 0.930
And I shutdown Tails and wait for the computer to power off 9.139
After features/support/hooks.rb:326 0.275
After features/support/hooks.rb:100 0.010
Tags: @product
2:53.311
Before features/support/hooks.rb:269 0.005
Given a computer 0.236
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.379
Then Tails is running from USB drive "old" 0.444
And all tps features are active 2.044
When I write some files expected to persist 2.327
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.700
And all persistence configuration files have safe access rights 0.428
And all persistent directories from the old Tails version have safe access rights 2.642
And I take note of which tps features are available 0.454
And I shutdown Tails and wait for the computer to power off 4.288
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.364
After features/support/hooks.rb:326 0.176
After features/support/hooks.rb:100 0.009
Tags: @product
2:43.943
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 24.713
And I log in to a new session 18.597
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.521
And I plug USB drive "to_upgrade" 2.409
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.641
Then the running Tails is installed on USB drive "to_upgrade" 22.620
And I unplug USB drive "to_upgrade" 0.223
And I unplug USB drive "__internal" 0.216
After features/support/hooks.rb:326 1.926
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.474
Before features/support/hooks.rb:269 0.006
Given a computer 0.204
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.758
Then all tps features from the old Tails version are active 2.097
And Tails is running from USB drive "to_upgrade" 0.359
And the boot device has safe access rights 3.822
And the expected persistent files created with the old Tails version are present in the filesystem 1.635
And all persistent directories from the old Tails version have safe access rights 2.597
After features/support/hooks.rb:326 0.998
After features/support/hooks.rb:100 0.031
Tags: @product @automatic_upgrade
6:27.969
Before features/support/hooks.rb:269 0.013
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.966
And no SquashFS delta is installed 0.092
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.549
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.277
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.491
When the network is plugged 0.085
And Tor is ready 20.178
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.428
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.754
Given I shutdown Tails and wait for the computer to power off 11.251
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.267
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.249
And the file system changes introduced in version 6.2~testoverlayfs are present 0.329
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.309
# 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.309
When the network is plugged 0.097
And Tor is ready 15.465
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.880
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.128
Given I shutdown Tails and wait for the computer to power off 4.695
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.638
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.364
And the file system changes introduced in version 6.3~testoverlayfs are present 0.524
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.347
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.293
When the network is plugged 0.090
And Tor is ready 19.925
Then the Upgrader considers the system as up-to-date 0.354
# 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.428
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.960
After features/support/hooks.rb:326 0.983
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
38.055
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 12.037
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.327
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.067
But a current signing key is available on our website 0.000
When the network is plugged 0.074
And Tor is ready 18.857
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.639
After features/support/hooks.rb:326 1.290
After features/support/hooks.rb:100 0.000