Project Number Date
test_Tails_ISO_stable 5441 03 Feb 2025, 23:01

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.171 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:15.357
Before features/support/hooks.rb:269 0.006
Given a computer 0.215
And I create a 7200 MiB disk named "old" 0.039
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 31.926
When I start Tails from USB drive "old" with network unplugged 1:37.776
Then the boot device has safe access rights 3.324
And Tails is running from USB drive "old" 0.308
And there is no persistence partition on USB drive "old" 0.080
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.299
And I unplug USB drive "old" 0.249
After features/support/hooks.rb:326 3.515
After features/support/hooks.rb:100 0.007
Tags: @product
2:14.248
Before features/support/hooks.rb:269 0.003
Given a computer 0.166
And I start Tails from USB drive "old" with network unplugged and I login 1:28.881
Then Tails is running from USB drive "old" 0.320
And I create a persistent partition 34.085
And I take note of which tps features are available 1.386
Then a Tails persistence partition exists on USB drive "old" 0.849
And I shutdown Tails and wait for the computer to power off 8.558
After features/support/hooks.rb:326 0.141
After features/support/hooks.rb:100 0.008
Tags: @product
2:57.263
Before features/support/hooks.rb:269 0.005
Given a computer 0.175
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.786
Then Tails is running from USB drive "old" 0.759
And all tps features are active 2.111
When I write some files expected to persist 2.186
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.240
And all persistence configuration files have safe access rights 0.403
And all persistent directories from the old Tails version have safe access rights 2.644
And I take note of which tps features are available 0.421
And I shutdown Tails and wait for the computer to power off 4.524
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.011
After features/support/hooks.rb:326 0.150
After features/support/hooks.rb:100 0.009
Tags: @product
2:29.985
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.886
And I log in to a new session 19.598
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.146
And I plug USB drive "to_upgrade" 2.439
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.770
Then the running Tails is installed on USB drive "to_upgrade" 19.724
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.214
After features/support/hooks.rb:326 6.854
After features/support/hooks.rb:100 0.000
Tags: @product
2:25.460
Before features/support/hooks.rb:269 0.006
Given a computer 0.202
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:15.706
Then all tps features from the old Tails version are active 1.839
And Tails is running from USB drive "to_upgrade" 0.390
And the boot device has safe access rights 3.238
And the expected persistent files created with the old Tails version are present in the filesystem 1.540
And all persistent directories from the old Tails version have safe access rights 2.541
After features/support/hooks.rb:326 1.001
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:42.440
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.749
And no SquashFS delta is installed 0.401
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.343
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.120
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.409
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.485
When the network is plugged 0.085
And Tor is ready 20.103
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.034
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.946
Given I shutdown Tails and wait for the computer to power off 9.075
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.997
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.934
And the file system changes introduced in version 6.2~testoverlayfs are present 0.345
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# 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.281
When the network is plugged 0.070
And Tor is ready 49.173
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.583
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.247
Given I shutdown Tails and wait for the computer to power off 4.532
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.895
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.185
And the file system changes introduced in version 6.3~testoverlayfs are present 0.501
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.292
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.274
When the network is plugged 0.075
And Tor is ready 21.013
Then the Upgrader considers the system as up-to-date 0.347
# 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.540
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.904
After features/support/hooks.rb:326 0.780
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
37.414
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.626
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.605
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 0.073
But a current signing key is available on our website 0.000
When the network is plugged 0.095
And Tor is ready 18.290
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.656
After features/support/hooks.rb:326 0.912
After features/support/hooks.rb:100 0.000