Project Number Date
test_Tails_ISO_test-suite-options 16 02 Jul 2025, 21:33

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 28:44.606 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:57.401
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.208
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.061
And I write an old version of the Tails USB image to disk "old" 41.388
When I start Tails from USB drive "old" with network unplugged 2:6.978
Then the boot device has safe access rights 6.574
And Tails is running from USB drive "old" 0.392
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.101
And udev-watchdog is monitoring the correct device 0.319
And I unplug USB drive "old" 0.261
After features/support/hooks.rb:330 3.760
After features/support/hooks.rb:100 0.016
Tags: @product
3:15.008
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given a computer 0.295
And I start Tails from USB drive "old" with network unplugged and I login 2:12.212
Then Tails is running from USB drive "old" 1.245
And I create a persistent partition 45.533
And I take note of which tps features are available 3.055
Then a Tails persistence partition exists on USB drive "old" 1.022
And I shutdown Tails and wait for the computer to power off 11.643
After features/support/hooks.rb:330 0.276
After features/support/hooks.rb:100 0.061
Tags: @product
4:19.911
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.207
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:18.280
Then Tails is running from USB drive "old" 1.216
And all tps features are active 2.283
When I write some files expected to persist 1.870
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.245
And all persistence configuration files have safe access rights 0.602
And all persistent directories from the old Tails version have safe access rights 3.722
And I take note of which tps features are available 0.598
And I shutdown Tails and wait for the computer to power off 9.277
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 41.604
After features/support/hooks.rb:330 0.167
After features/support/hooks.rb:100 0.010
Tags: @product
3:39.464
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 11.995
And I log in to a new session 31.688
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.585
And I plug USB drive "to_upgrade" 3.345
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:55.608
Then the running Tails is installed on USB drive "to_upgrade" 53.530
And I unplug USB drive "to_upgrade" 0.340
And I unplug USB drive "__internal" 0.371
After features/support/hooks.rb:330 2.098
After features/support/hooks.rb:100 0.000
Tags: @product
3:5.651
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.230
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:49.786
Then all tps features from the old Tails version are active 4.730
And Tails is running from USB drive "to_upgrade" 0.744
And the boot device has safe access rights 4.751
And the expected persistent files created with the old Tails version are present in the filesystem 1.693
And all persistent directories from the old Tails version have safe access rights 3.714
After features/support/hooks.rb:330 4.124
After features/support/hooks.rb:100 0.469
Tags: @product @automatic_upgrade
10:11.431
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.016
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 17.170
And no SquashFS delta is installed 1.552
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 2.397
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.629
And the file system changes introduced in version 6.2~testoverlayfs are not present 1.145
And the file system changes introduced in version 6.3~testoverlayfs are not present 1.844
When the network is plugged 0.162
And Tor is ready 26.431
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 15.294
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 19.954
Given I shutdown Tails and wait for the computer to power off 13.595
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:59.594
Then Tails is running version 6.2~testoverlayfs 0.254
And all tps features are active 6.567
And the file system changes introduced in version 6.2~testoverlayfs are present 0.815
And only the 6.2~testoverlayfs SquashFS delta is installed 0.138
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.311
# 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.322
When the network is plugged 0.075
And Tor is ready 57.656
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.437
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 15.259
Given I shutdown Tails and wait for the computer to power off 7.017
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:46.777
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 6.550
And the file system changes introduced in version 6.3~testoverlayfs are present 2.749
And only the 6.3~testoverlayfs SquashFS delta is installed 0.129
# 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.502
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.520
When the network is plugged 0.102
And Tor is ready 30.711
Then the Upgrader considers the system as up-to-date 0.699
# 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 30.942
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.101
After features/support/hooks.rb:330 1.043
After features/support/hooks.rb:100 0.030
Tags: @product @automatic_upgrade
1:15.738
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 18.791
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.412
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.117
And the signing key used by the Upgrader is outdated 0.091
But a current signing key is available on our website 0.000
When the network is plugged 0.077
And Tor is ready 38.220
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 18.027
After features/support/hooks.rb:330 1.037
After features/support/hooks.rb:100 0.000