Project Number Date
test_Tails_ISO_stable 5256 08 Nov 2024, 12:39

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 20:7.478 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:45.661
Before features/support/hooks.rb:269 0.006
Given a computer 0.216
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 31.095
When I start Tails from USB drive "old" with network unplugged 2:8.517
Then the boot device has safe access rights 3.611
And Tails is running from USB drive "old" 0.355
And there is no persistence partition on USB drive "old" 0.093
And process "udev-watchdog" is running 0.108
And udev-watchdog is monitoring the correct device 0.349
And I unplug USB drive "old" 0.208
After features/support/hooks.rb:326 3.791
After features/support/hooks.rb:100 0.013
Tags: @product
2:6.714
Before features/support/hooks.rb:269 0.008
Given a computer 0.237
And I start Tails from USB drive "old" with network unplugged and I login 1:22.426
Then Tails is running from USB drive "old" 0.442
And I create a persistent partition 33.205
And I take note of which tps features are available 1.896
Then a Tails persistence partition exists on USB drive "old" 0.921
And I shutdown Tails and wait for the computer to power off 7.583
After features/support/hooks.rb:326 0.271
After features/support/hooks.rb:100 0.013
Tags: @product
2:55.072
Before features/support/hooks.rb:269 0.007
Given a computer 0.316
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.168
Then Tails is running from USB drive "old" 0.717
And all tps features are active 2.035
When I write some files expected to persist 1.940
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.307
And all persistence configuration files have safe access rights 0.446
And all persistent directories from the old Tails version have safe access rights 3.370
And I take note of which tps features are available 0.540
And I shutdown Tails and wait for the computer to power off 5.269
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.961
After features/support/hooks.rb:326 0.160
After features/support/hooks.rb:100 0.009
Tags: @product
2:42.591
Before features/support/hooks.rb:269 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 12.226
And I log in to a new session 23.719
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.847
And I plug USB drive "to_upgrade" 2.464
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.291
Then the running Tails is installed on USB drive "to_upgrade" 25.546
And I unplug USB drive "to_upgrade" 0.262
And I unplug USB drive "__internal" 0.231
After features/support/hooks.rb:326 4.800
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.411
Before features/support/hooks.rb:269 0.007
Given a computer 0.260
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.980
Then all tps features from the old Tails version are active 1.887
And Tails is running from USB drive "to_upgrade" 0.371
And the boot device has safe access rights 3.343
And the expected persistent files created with the old Tails version are present in the filesystem 1.667
And all persistent directories from the old Tails version have safe access rights 2.898
After features/support/hooks.rb:326 0.614
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:42.310
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 13.981
And no SquashFS delta is installed 0.096
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.389
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.147
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.496
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.509
When the network is plugged 0.072
And Tor is ready 21.210
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.886
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.910
Given I shutdown Tails and wait for the computer to power off 13.502
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.387
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.505
And the file system changes introduced in version 6.2~testoverlayfs are present 0.333
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.313
# 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.319
When the network is plugged 0.076
And Tor is ready 18.021
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.310
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.466
Given I shutdown Tails and wait for the computer to power off 6.466
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.415
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.250
And the file system changes introduced in version 6.3~testoverlayfs are present 0.574
And only the 6.3~testoverlayfs SquashFS delta is installed 0.087
# 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.434
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.327
When the network is plugged 0.099
And Tor is ready 20.595
Then the Upgrader considers the system as up-to-date 0.302
# 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.629
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.087
After features/support/hooks.rb:326 0.783
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
38.716
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 10.697
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.418
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the signing key used by the Upgrader is outdated 0.875
But a current signing key is available on our website 0.000
When the network is plugged 0.085
And Tor is ready 19.684
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.883
After features/support/hooks.rb:326 0.713
After features/support/hooks.rb:100 0.000