Project Number Date
test_Tails_ISO_stable 5626 05 May 2025, 15: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:40.191 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:9.426
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.210
And I create a 7200 MiB disk named "old" 0.061
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 29.949
When I start Tails from USB drive "old" with network unplugged 1:34.159
Then the boot device has safe access rights 2.997
And Tails is running from USB drive "old" 0.348
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.305
And I unplug USB drive "old" 0.177
After features/support/hooks.rb:330 6.828
After features/support/hooks.rb:100 0.058
Tags: @product
2:9.258
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login 1:25.637
Then Tails is running from USB drive "old" 0.354
And I create a persistent partition 31.664
And I take note of which tps features are available 2.078
Then a Tails persistence partition exists on USB drive "old" 0.822
And I shutdown Tails and wait for the computer to power off 8.505
After features/support/hooks.rb:330 0.211
After features/support/hooks.rb:100 0.008
Tags: @product
2:54.798
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.330
Then Tails is running from USB drive "old" 0.363
And all tps features are active 2.274
When I write some files expected to persist 1.689
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.249
And all persistence configuration files have safe access rights 0.376
And all persistent directories from the old Tails version have safe access rights 2.434
And I take note of which tps features are available 0.518
And I shutdown Tails and wait for the computer to power off 4.252
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.127
After features/support/hooks.rb:330 0.136
After features/support/hooks.rb:100 0.008
Tags: @product
2:40.724
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 9.780
And I log in to a new session 25.491
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.569
And I plug USB drive "to_upgrade" 2.394
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.618
Then the running Tails is installed on USB drive "to_upgrade" 27.399
And I unplug USB drive "to_upgrade" 0.245
And I unplug USB drive "__internal" 0.222
After features/support/hooks.rb:330 2.101
After features/support/hooks.rb:100 0.000
Tags: @product
2:25.350
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.224
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:15.169
Then all tps features from the old Tails version are active 1.864
And Tails is running from USB drive "to_upgrade" 0.331
And the boot device has safe access rights 3.533
And the expected persistent files created with the old Tails version are present in the filesystem 1.457
And all persistent directories from the old Tails version have safe access rights 2.769
After features/support/hooks.rb:330 2.093
After features/support/hooks.rb:100 0.011
6:42.291
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.913
And no SquashFS delta is installed 0.069
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.105
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.464
When the network is plugged 0.066
And Tor is ready 26.423
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.939
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.763
Given I shutdown Tails and wait for the computer to power off 11.076
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.883
Then Tails is running version 6.2~testoverlayfs 0.027
And all tps features are active 2.309
And the file system changes introduced in version 6.2~testoverlayfs are present 0.359
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.335
# 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.317
When the network is plugged 0.091
And Tor is ready 20.387
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.361
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.246
Given I shutdown Tails and wait for the computer to power off 8.333
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.223
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.174
And the file system changes introduced in version 6.3~testoverlayfs are present 0.533
And only the 6.3~testoverlayfs SquashFS delta is installed 0.088
# 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.339
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.276
When the network is plugged 0.080
And Tor is ready 19.481
Then the Upgrader considers the system as up-to-date 0.337
# 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.961
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.651
After features/support/hooks.rb:330 0.721
After features/support/hooks.rb:100 0.019
38.342
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.428
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.365
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.109
And the signing key used by the Upgrader is outdated 0.122
But a current signing key is available on our website 0.000
When the network is plugged 0.127
And Tor is ready 19.607
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.582
After features/support/hooks.rb:330 2.119
After features/support/hooks.rb:100 0.000