Project Number Date
test_Tails_ISO_stable 5641 12 May 2025, 13:10

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 21:57.848 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:51.615
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.015
Given a computer 0.285
And I create a 7200 MiB disk named "old" 0.072
And I plug USB drive "old" 1.073
And I write an old version of the Tails USB image to disk "old" 1:0.772
When I start Tails from USB drive "old" with network unplugged 1:45.038
Then the boot device has safe access rights 3.280
And Tails is running from USB drive "old" 0.371
And there is no persistence partition on USB drive "old" 0.083
And process "udev-watchdog" is running 0.112
And udev-watchdog is monitoring the correct device 0.318
And I unplug USB drive "old" 0.208
After features/support/hooks.rb:330 3.779
After features/support/hooks.rb:100 0.009
Tags: @product
2:30.470
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.281
And I start Tails from USB drive "old" with network unplugged and I login 1:40.749
Then Tails is running from USB drive "old" 0.384
And I create a persistent partition 33.724
And I take note of which tps features are available 3.047
Then a Tails persistence partition exists on USB drive "old" 1.030
And I shutdown Tails and wait for the computer to power off 11.253
After features/support/hooks.rb:330 0.236
After features/support/hooks.rb:100 0.012
Tags: @product
3:32.320
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.427
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:46.061
Then Tails is running from USB drive "old" 1.064
And all tps features are active 3.284
When I write some files expected to persist 2.026
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.264
And all persistence configuration files have safe access rights 0.610
And all persistent directories from the old Tails version have safe access rights 3.191
And I take note of which tps features are available 1.600
And I shutdown Tails and wait for the computer to power off 6.533
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 27.257
After features/support/hooks.rb:330 0.169
After features/support/hooks.rb:100 0.011
Tags: @product
2:45.890
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.698
And I log in to a new session 22.951
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.572
And I plug USB drive "to_upgrade" 2.633
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.078
Then the running Tails is installed on USB drive "to_upgrade" 27.470
And I unplug USB drive "to_upgrade" 0.264
And I unplug USB drive "__internal" 0.219
After features/support/hooks.rb:330 3.630
After features/support/hooks.rb:100 0.000
Tags: @product
2:32.335
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.214
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:21.226
Then all tps features from the old Tails version are active 2.295
And Tails is running from USB drive "to_upgrade" 0.480
And the boot device has safe access rights 3.484
And the expected persistent files created with the old Tails version are present in the filesystem 1.663
And all persistent directories from the old Tails version have safe access rights 2.969
After features/support/hooks.rb:330 1.475
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
7:5.458
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.016
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.374
And no SquashFS delta is installed 0.164
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.511
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.097
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.307
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.497
When the network is plugged 0.062
And Tor is ready 20.872
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.674
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.066
Given I shutdown Tails and wait for the computer to power off 9.794
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.946
Then Tails is running version 6.2~testoverlayfs 0.075
And all tps features are active 2.420
And the file system changes introduced in version 6.2~testoverlayfs are present 0.472
And only the 6.2~testoverlayfs SquashFS delta is installed 0.092
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.405
# 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.434
When the network is plugged 0.076
And Tor is ready 17.715
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.092
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.933
Given I shutdown Tails and wait for the computer to power off 4.503
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.304
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.771
And the file system changes introduced in version 6.3~testoverlayfs are present 0.683
And only the 6.3~testoverlayfs SquashFS delta is installed 0.134
# 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.364
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.372
When the network is plugged 0.509
And Tor is ready 18.645
Then the Upgrader considers the system as up-to-date 0.333
# 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 16.980
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.750
After features/support/hooks.rb:330 0.754
After features/support/hooks.rb:100 0.033
Tags: @product @automatic_upgrade
39.757
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.013
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.750
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.486
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.088
And the signing key used by the Upgrader is outdated 0.117
But a current signing key is available on our website 0.000
When the network is plugged 0.100
And Tor is ready 19.323
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.891
After features/support/hooks.rb:330 2.320
After features/support/hooks.rb:100 0.000