Project Number Date
test_Tails_ISO_stable 5536 28 Mar 2025, 12:47

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:13.838 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:1.499
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.174
And I create a 7200 MiB disk named "old" 0.038
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 30.197
When I start Tails from USB drive "old" with network unplugged 1:26.139
Then the boot device has safe access rights 2.949
And Tails is running from USB drive "old" 0.312
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.291
And I unplug USB drive "old" 0.183
After features/support/hooks.rb:330 0.893
After features/support/hooks.rb:100 0.013
Tags: @product
2:3.227
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.171
And I start Tails from USB drive "old" with network unplugged and I login 1:21.650
Then Tails is running from USB drive "old" 0.331
And I create a persistent partition 30.818
And I take note of which tps features are available 1.262
Then a Tails persistence partition exists on USB drive "old" 0.778
And I shutdown Tails and wait for the computer to power off 8.213
After features/support/hooks.rb:330 0.144
After features/support/hooks.rb:100 0.009
Tags: @product
2:48.957
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.835
Then Tails is running from USB drive "old" 0.486
And all tps features are active 1.738
When I write some files expected to persist 1.686
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.225
And all persistence configuration files have safe access rights 0.581
And all persistent directories from the old Tails version have safe access rights 2.673
And I take note of which tps features are available 0.419
And I shutdown Tails and wait for the computer to power off 4.332
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.785
After features/support/hooks.rb:330 0.098
After features/support/hooks.rb:100 0.010
Tags: @product
2:31.900
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 9.783
And I log in to a new session 18.592
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.781
And I plug USB drive "to_upgrade" 2.410
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.202
Then the running Tails is installed on USB drive "to_upgrade" 23.664
And I unplug USB drive "to_upgrade" 0.227
And I unplug USB drive "__internal" 0.237
After features/support/hooks.rb:330 0.874
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.864
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.180
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.661
Then all tps features from the old Tails version are active 1.748
And Tails is running from USB drive "to_upgrade" 0.301
And the boot device has safe access rights 3.152
And the expected persistent files created with the old Tails version are present in the filesystem 1.428
And all persistent directories from the old Tails version have safe access rights 2.391
After features/support/hooks.rb:330 0.915
After features/support/hooks.rb:100 0.028
6:45.751
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 11.267
And no SquashFS delta is installed 0.062
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.277
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.083
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.431
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.492
When the network is plugged 0.064
And Tor is ready 18.378
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.755
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.637
Given I shutdown Tails and wait for the computer to power off 8.448
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.656
Then Tails is running version 6.2~testoverlayfs 0.032
And all tps features are active 1.868
And the file system changes introduced in version 6.2~testoverlayfs are present 0.288
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.356
# 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.295
When the network is plugged 0.073
And Tor is ready 16.958
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.077
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.743
Given I shutdown Tails and wait for the computer to power off 4.219
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.966
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.913
And the file system changes introduced in version 6.3~testoverlayfs are present 0.513
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.287
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.295
When the network is plugged 0.083
And Tor is ready 45.305
Then the Upgrader considers the system as up-to-date 0.316
# 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 14.746
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.680
After features/support/hooks.rb:330 0.773
After features/support/hooks.rb:100 0.019
39.637
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 9.836
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.309
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.069
But a current signing key is available on our website 0.000
When the network is plugged 0.087
And Tor is ready 21.499
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.775
After features/support/hooks.rb:330 0.673
After features/support/hooks.rb:100 0.000