Project Number Date
test_Tails_ISO_stable 4848 19 May 2024, 12:45

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 17:58.103 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
1:54.353
Before features/support/hooks.rb:259 0.005
Given a computer 0.175
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 29.244
When I start Tails from USB drive "old" with network unplugged 1:19.920
Then the boot device has safe access rights 2.976
And Tails is running from USB drive "old" 0.325
And there is no persistence partition on USB drive "old" 0.055
And process "udev-watchdog" is running 0.082
And udev-watchdog is monitoring the correct device 0.287
And I unplug USB drive "old" 0.192
After features/support/hooks.rb:305 7.163
After features/support/hooks.rb:89 0.014
Tags: @product
2:7.159
Before features/support/hooks.rb:259 0.004
Given a computer 0.162
And I start Tails from USB drive "old" with network unplugged and I login 1:21.015
Then Tails is running from USB drive "old" 0.303
And I create a persistent partition 35.061
And I take note of which tps features are available 1.481
Then a Tails persistence partition exists on USB drive "old" 0.834
And I shutdown Tails and wait for the computer to power off 8.300
After features/support/hooks.rb:305 0.147
After features/support/hooks.rb:89 0.009
Tags: @product
2:42.035
Before features/support/hooks.rb:259 0.006
Given a computer 0.170
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:5.868
Then Tails is running from USB drive "old" 0.330
And all tps features are active 2.280
When I write some files expected to persist 1.590
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.208
And all persistence configuration files have safe access rights 0.348
And all persistent directories from the old Tails version have safe access rights 2.196
And I take note of which tps features are available 0.409
And I shutdown Tails and wait for the computer to power off 4.313
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.317
After features/support/hooks.rb:305 0.084
After features/support/hooks.rb:89 0.009
Tags: @product
2:20.389
Before features/support/hooks.rb:259 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.195
And I log in to a new session 16.104
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.634
And I plug USB drive "to_upgrade" 2.414
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.361
Then the running Tails is installed on USB drive "to_upgrade" 16.302
And I unplug USB drive "to_upgrade" 0.189
And I unplug USB drive "__internal" 0.186
After features/support/hooks.rb:305 2.521
After features/support/hooks.rb:89 0.000
Tags: @product
2:4.329
Before features/support/hooks.rb:259 0.014
Given a computer 0.197
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:55.356
Then all tps features from the old Tails version are active 1.477
And Tails is running from USB drive "to_upgrade" 0.320
And the boot device has safe access rights 3.066
And the expected persistent files created with the old Tails version are present in the filesystem 1.618
And all persistent directories from the old Tails version have safe access rights 2.291
After features/support/hooks.rb:305 0.531
After features/support/hooks.rb:89 0.011
Tags: @product @automatic_upgrade
6:14.229
Before features/support/hooks.rb:259 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.657
And no SquashFS delta is installed 0.061
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.283
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.271
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.413
When the network is plugged 0.038
And Tor is ready 18.133
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.660
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.904
Given I shutdown Tails and wait for the computer to power off 8.759
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.648
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.151
And the file system changes introduced in version 6.2~testoverlayfs are present 0.299
And only the 6.2~testoverlayfs SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.340
# 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.279
When the network is plugged 0.041
And Tor is ready 17.320
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.582
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.050
Given I shutdown Tails and wait for the computer to power off 4.327
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.637
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.863
And the file system changes introduced in version 6.3~testoverlayfs are present 0.473
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.327
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.238
When the network is plugged 0.036
And Tor is ready 17.060
Then the Upgrader considers the system as up-to-date 0.349
# 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.798
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.981
After features/support/hooks.rb:305 0.703
After features/support/hooks.rb:89 0.021
Tags: @product @automatic_upgrade
35.607
Before features/support/hooks.rb:259 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.907
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.325
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.430
But a current signing key is available on our website 0.000
When the network is plugged 0.033
And Tor is ready 18.280
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.572
After features/support/hooks.rb:305 0.658
After features/support/hooks.rb:89 0.000