Project Number Date
test_Tails_ISO_test-suite-options 20 06 Jul 2025, 21:26

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 27:42.801 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:55.150
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.205
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.060
And I write an old version of the Tails USB image to disk "old" 39.588
When I start Tails from USB drive "old" with network unplugged 2:2.508
Then the boot device has safe access rights 9.832
And Tails is running from USB drive "old" 0.788
And there is no persistence partition on USB drive "old" 0.136
And process "udev-watchdog" is running 0.151
And udev-watchdog is monitoring the correct device 0.602
And I unplug USB drive "old" 0.234
After features/support/hooks.rb:330 7.661
After features/support/hooks.rb:100 0.017
Tags: @product
3:9.812
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.527
And I start Tails from USB drive "old" with network unplugged and I login 2:2.546
Then Tails is running from USB drive "old" 2.776
And I create a persistent partition 48.854
And I take note of which tps features are available 2.624
Then a Tails persistence partition exists on USB drive "old" 0.968
And I shutdown Tails and wait for the computer to power off 11.513
After features/support/hooks.rb:330 0.972
After features/support/hooks.rb:100 0.025
Tags: @product
4:24.059
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.016
Given a computer 0.546
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:21.625
Then Tails is running from USB drive "old" 0.941
And all tps features are active 2.246
When I write some files expected to persist 2.123
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.424
And all persistence configuration files have safe access rights 0.686
And all persistent directories from the old Tails version have safe access rights 3.171
And I take note of which tps features are available 0.825
And I shutdown Tails and wait for the computer to power off 8.150
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 43.316
After features/support/hooks.rb:330 0.146
After features/support/hooks.rb:100 0.008
Tags: @product
3:16.892
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 16.351
And I log in to a new session 25.389
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.172
And I plug USB drive "to_upgrade" 2.575
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:50.881
Then the running Tails is installed on USB drive "to_upgrade" 38.730
And I unplug USB drive "to_upgrade" 0.227
And I unplug USB drive "__internal" 0.562
After features/support/hooks.rb:330 2.810
After features/support/hooks.rb:100 0.000
Tags: @product
3:17.538
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.224
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:0.266
Then all tps features from the old Tails version are active 1.899
And Tails is running from USB drive "to_upgrade" 0.333
And the boot device has safe access rights 4.104
And the expected persistent files created with the old Tails version are present in the filesystem 2.374
And all persistent directories from the old Tails version have safe access rights 8.335
After features/support/hooks.rb:330 1.022
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
9:43.428
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 17.945
And no SquashFS delta is installed 0.353
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.403
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.155
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.768
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.731
When the network is plugged 0.076
And Tor is ready 33.350
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.487
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 21.378
Given I shutdown Tails and wait for the computer to power off 16.246
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:4.899
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 3.336
And the file system changes introduced in version 6.2~testoverlayfs are present 0.384
And only the 6.2~testoverlayfs SquashFS delta is installed 0.087
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.331
# 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.318
When the network is plugged 0.077
And Tor is ready 26.780
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.125
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 15.840
Given I shutdown Tails and wait for the computer to power off 6.547
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:1.508
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.230
And the file system changes introduced in version 6.3~testoverlayfs are present 2.811
And only the 6.3~testoverlayfs SquashFS delta is installed 0.935
# 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 1.028
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 1.630
When the network is plugged 0.276
And Tor is ready 22.929
Then the Upgrader considers the system as up-to-date 0.426
# 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 22.062
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.926
After features/support/hooks.rb:330 0.711
After features/support/hooks.rb:100 0.044
Tags: @product @automatic_upgrade
55.921
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 13.643
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.542
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 0.161
But a current signing key is available on our website 0.000
When the network is plugged 0.087
And Tor is ready 26.709
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 13.631
After features/support/hooks.rb:330 1.099
After features/support/hooks.rb:100 0.000