Project Number Date
test_Tails_ISO_test-suite-options 10 26 Jun 2025, 19:59

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:42.521 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:5.174
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.178
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 30.897
When I start Tails from USB drive "old" with network unplugged 1:28.849
Then the boot device has safe access rights 3.096
And Tails is running from USB drive "old" 0.339
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.113
And udev-watchdog is monitoring the correct device 0.350
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:330 3.608
After features/support/hooks.rb:100 0.010
Tags: @product
2:7.620
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.178
And I start Tails from USB drive "old" with network unplugged and I login 1:25.886
Then Tails is running from USB drive "old" 0.356
And I create a persistent partition 30.609
And I take note of which tps features are available 1.622
Then a Tails persistence partition exists on USB drive "old" 0.729
And I shutdown Tails and wait for the computer to power off 8.237
After features/support/hooks.rb:330 0.155
After features/support/hooks.rb:100 0.009
Tags: @product
2:55.956
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.473
Then Tails is running from USB drive "old" 1.074
And all tps features are active 2.059
When I write some files expected to persist 3.254
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.276
And all persistence configuration files have safe access rights 0.478
And all persistent directories from the old Tails version have safe access rights 3.458
And I take note of which tps features are available 0.433
And I shutdown Tails and wait for the computer to power off 4.474
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.770
After features/support/hooks.rb:330 0.104
After features/support/hooks.rb:100 0.010
Tags: @product
2:36.148
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 10.355
And I log in to a new session 19.412
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.767
And I plug USB drive "to_upgrade" 2.592
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.503
Then the running Tails is installed on USB drive "to_upgrade" 26.104
And I unplug USB drive "to_upgrade" 0.214
And I unplug USB drive "__internal" 0.197
After features/support/hooks.rb:330 1.909
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.212
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.183
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.632
Then all tps features from the old Tails version are active 1.735
And Tails is running from USB drive "to_upgrade" 0.375
And the boot device has safe access rights 3.240
And the expected persistent files created with the old Tails version are present in the filesystem 1.567
And all persistent directories from the old Tails version have safe access rights 2.477
After features/support/hooks.rb:330 1.108
After features/support/hooks.rb:100 0.010
7:3.167
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 with a persistent partition enabled and logged in 12.013
And no SquashFS delta is installed 0.127
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.344
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.079
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.374
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.479
When the network is plugged 0.083
And Tor is ready 48.017
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.570
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.950
Given I shutdown Tails and wait for the computer to power off 8.494
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.484
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.123
And the file system changes introduced in version 6.2~testoverlayfs are present 0.332
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.350
# 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.253
When the network is plugged 0.100
And Tor is ready 21.564
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.567
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.575
Given I shutdown Tails and wait for the computer to power off 6.529
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.163
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 1.827
And the file system changes introduced in version 6.3~testoverlayfs are present 0.521
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.294
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.293
When the network is plugged 0.062
And Tor is ready 22.458
Then the Upgrader considers the system as up-to-date 0.340
# 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.987
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.630
After features/support/hooks.rb:330 0.749
After features/support/hooks.rb:100 0.018
37.242
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.799
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.366
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.100
But a current signing key is available on our website 0.000
When the network is plugged 0.097
And Tor is ready 18.789
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.038
After features/support/hooks.rb:330 0.762
After features/support/hooks.rb:100 0.000