Project Number Date
test_Tails_ISO_stable 5003 06 Aug 2024, 16:16

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:39.184 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:42.357
Before features/support/hooks.rb:269 0.006
Given a computer 0.219
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 50.930
When I start Tails from USB drive "old" with network unplugged 1:45.307
Then the boot device has safe access rights 3.623
And Tails is running from USB drive "old" 0.402
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.354
And I unplug USB drive "old" 0.254
After features/support/hooks.rb:326 3.908
After features/support/hooks.rb:100 0.018
Tags: @product
2:9.749
Before features/support/hooks.rb:269 0.011
Given a computer 0.307
And I start Tails from USB drive "old" with network unplugged and I login 1:23.421
Then Tails is running from USB drive "old" 0.323
And I create a persistent partition 33.880
And I take note of which tps features are available 2.027
Then a Tails persistence partition exists on USB drive "old" 0.924
And I shutdown Tails and wait for the computer to power off 8.864
After features/support/hooks.rb:326 0.198
After features/support/hooks.rb:100 0.013
Tags: @product
2:56.336
Before features/support/hooks.rb:269 0.009
Given a computer 0.270
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.399
Then Tails is running from USB drive "old" 0.433
And all tps features are active 3.345
When I write some files expected to persist 1.975
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.308
And all persistence configuration files have safe access rights 0.419
And all persistent directories from the old Tails version have safe access rights 2.605
And I take note of which tps features are available 0.619
And I shutdown Tails and wait for the computer to power off 4.569
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.389
After features/support/hooks.rb:326 0.142
After features/support/hooks.rb:100 0.014
Tags: @product
2:33.160
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.002
And I log in to a new session 19.668
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.688
And I plug USB drive "to_upgrade" 2.438
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.469
Then the running Tails is installed on USB drive "to_upgrade" 20.377
And I unplug USB drive "to_upgrade" 0.221
And I unplug USB drive "__internal" 0.293
After features/support/hooks.rb:326 3.642
After features/support/hooks.rb:100 0.000
Tags: @product
2:23.789
Before features/support/hooks.rb:269 0.012
Given a computer 0.291
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.895
Then all tps features from the old Tails version are active 1.827
And Tails is running from USB drive "to_upgrade" 0.530
And the boot device has safe access rights 4.564
And the expected persistent files created with the old Tails version are present in the filesystem 1.778
And all persistent directories from the old Tails version have safe access rights 2.901
After features/support/hooks.rb:326 0.771
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
7:14.849
Before features/support/hooks.rb:269 0.014
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.962
And no SquashFS delta is installed 0.116
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.366
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.278
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.468
When the network is plugged 0.183
And Tor is ready 50.670
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.665
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.212
Given I shutdown Tails and wait for the computer to power off 8.923
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.344
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.341
And the file system changes introduced in version 6.2~testoverlayfs are present 0.341
And only the 6.2~testoverlayfs SquashFS delta is installed 0.095
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.381
# 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.265
When the network is plugged 0.073
And Tor is ready 20.513
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.413
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.313
Given I shutdown Tails and wait for the computer to power off 4.474
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.666
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.583
And the file system changes introduced in version 6.3~testoverlayfs are present 0.562
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.482
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.245
When the network is plugged 0.033
And Tor is ready 16.827
Then the Upgrader considers the system as up-to-date 10.806
# 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.051
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.001
After features/support/hooks.rb:326 0.792
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
38.941
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.647
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.684
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.145
And the signing key used by the Upgrader is outdated 1.260
But a current signing key is available on our website 0.000
When the network is plugged 0.036
And Tor is ready 20.073
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.093
After features/support/hooks.rb:326 1.264
After features/support/hooks.rb:100 0.000