Project Number Date
test_Tails_ISO_devel 3740 15 Mar 2025, 13:11

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:6.863 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:20.171
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.219
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 32.716
When I start Tails from USB drive "old" with network unplugged 1:41.540
Then the boot device has safe access rights 3.444
And Tails is running from USB drive "old" 0.370
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.114
And udev-watchdog is monitoring the correct device 0.379
And I unplug USB drive "old" 0.207
After features/support/hooks.rb:330 3.749
After features/support/hooks.rb:100 0.010
Tags: @product
2:13.483
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.331
And I start Tails from USB drive "old" with network unplugged and I login 1:27.632
Then Tails is running from USB drive "old" 0.365
And I create a persistent partition 32.514
And I take note of which tps features are available 2.121
Then a Tails persistence partition exists on USB drive "old" 0.979
And I shutdown Tails and wait for the computer to power off 9.539
After features/support/hooks.rb:330 0.174
After features/support/hooks.rb:100 0.012
Tags: @product
2:57.422
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.268
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.046
Then Tails is running from USB drive "old" 0.379
And all tps features are active 2.780
When I write some files expected to persist 2.170
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.341
And all persistence configuration files have safe access rights 0.380
And all persistent directories from the old Tails version have safe access rights 3.058
And I take note of which tps features are available 2.347
And I shutdown Tails and wait for the computer to power off 6.440
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.208
After features/support/hooks.rb:330 0.145
After features/support/hooks.rb:100 0.010
Tags: @product
2:32.713
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.980
And I log in to a new session 21.156
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.627
And I plug USB drive "to_upgrade" 2.488
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.765
Then the running Tails is installed on USB drive "to_upgrade" 18.272
And I unplug USB drive "to_upgrade" 0.197
And I unplug USB drive "__internal" 0.225
After features/support/hooks.rb:330 2.483
After features/support/hooks.rb:100 0.000
Tags: @product
2:32.413
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.218
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:21.880
Then all tps features from the old Tails version are active 1.896
And Tails is running from USB drive "to_upgrade" 0.390
And the boot device has safe access rights 3.973
And the expected persistent files created with the old Tails version are present in the filesystem 1.507
And all persistent directories from the old Tails version have safe access rights 2.546
After features/support/hooks.rb:330 1.047
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:51.100
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.300
And no SquashFS delta is installed 0.387
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.466
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.101
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.432
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.464
When the network is plugged 0.179
And Tor is ready 21.057
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.670
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.974
Given I shutdown Tails and wait for the computer to power off 14.457
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:19.250
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.300
And the file system changes introduced in version 6.2~testoverlayfs are present 0.328
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.297
# 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.286
When the network is plugged 0.074
And Tor is ready 18.007
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.563
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.212
Given I shutdown Tails and wait for the computer to power off 4.358
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.879
Then Tails is running version 6.3~testoverlayfs 0.020
And all tps features are active 2.039
And the file system changes introduced in version 6.3~testoverlayfs are present 0.552
And only the 6.3~testoverlayfs SquashFS delta is installed 0.085
# 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.424
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.355
When the network is plugged 0.073
And Tor is ready 19.307
Then the Upgrader considers the system as up-to-date 0.319
# 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.664
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.118
After features/support/hooks.rb:330 0.715
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
39.558
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.763
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.459
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.107
And the signing key used by the Upgrader is outdated 0.201
But a current signing key is available on our website 0.000
When the network is plugged 0.106
And Tor is ready 22.709
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.210
After features/support/hooks.rb:330 1.322
After features/support/hooks.rb:100 0.000