Project Number Date
test_Tails_ISO_stable 5416 24 Jan 2025, 12:42

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 18:50.642 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
1:59.374
Before features/support/hooks.rb:269 0.006
Given a computer 0.241
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 30.310
When I start Tails from USB drive "old" with network unplugged 1:23.552
Then the boot device has safe access rights 3.122
And Tails is running from USB drive "old" 0.334
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.105
And udev-watchdog is monitoring the correct device 0.331
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:326 7.121
After features/support/hooks.rb:100 0.008
Tags: @product
2:15.866
Before features/support/hooks.rb:269 0.007
Given a computer 0.221
And I start Tails from USB drive "old" with network unplugged and I login 1:31.770
Then Tails is running from USB drive "old" 0.316
And I create a persistent partition 32.504
And I take note of which tps features are available 1.798
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.432
After features/support/hooks.rb:326 0.219
After features/support/hooks.rb:100 0.007
Tags: @product
2:52.059
Before features/support/hooks.rb:269 0.004
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.277
Then Tails is running from USB drive "old" 0.548
And all tps features are active 2.018
When I write some files expected to persist 1.834
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.224
And all persistence configuration files have safe access rights 0.389
And all persistent directories from the old Tails version have safe access rights 2.755
And I take note of which tps features are available 0.493
And I shutdown Tails and wait for the computer to power off 4.294
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.028
After features/support/hooks.rb:326 0.141
After features/support/hooks.rb:100 0.010
Tags: @product
2:30.018
Before features/support/hooks.rb:269 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 10.373
And I log in to a new session 17.068
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.655
And I plug USB drive "to_upgrade" 2.350
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.949
Then the running Tails is installed on USB drive "to_upgrade" 22.218
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.198
After features/support/hooks.rb:326 2.249
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.937
Before features/support/hooks.rb:269 0.005
Given a computer 0.178
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.131
Then all tps features from the old Tails version are active 1.695
And Tails is running from USB drive "to_upgrade" 0.363
And the boot device has safe access rights 3.230
And the expected persistent files created with the old Tails version are present in the filesystem 1.451
And all persistent directories from the old Tails version have safe access rights 2.886
After features/support/hooks.rb:326 0.672
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
6:18.657
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 12.021
And no SquashFS delta is installed 0.153
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.444
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.088
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.312
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.493
When the network is plugged 0.079
And Tor is ready 23.680
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.372
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.495
Given I shutdown Tails and wait for the computer to power off 8.471
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.703
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.197
And the file system changes introduced in version 6.2~testoverlayfs are present 0.309
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.277
# 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.263
When the network is plugged 0.067
And Tor is ready 19.361
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.564
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.428
Given I shutdown Tails and wait for the computer to power off 4.235
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.829
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.128
And the file system changes introduced in version 6.3~testoverlayfs are present 0.519
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.290
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.277
When the network is plugged 0.089
And Tor is ready 18.822
Then the Upgrader considers the system as up-to-date 0.324
# 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.120
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.056
After features/support/hooks.rb:326 0.744
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
38.727
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.969
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.266
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.080
But a current signing key is available on our website 0.000
When the network is plugged 0.071
And Tor is ready 20.815
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.463
After features/support/hooks.rb:326 0.709
After features/support/hooks.rb:100 0.000