Project Number Date
test_Tails_ISO_stable 5956 15 Nov 2025, 14: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 16:7.767 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:14.025
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.161
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.039
And I write an old version of the Tails USB image to disk "old" 32.552
When I start Tails from USB drive "old" with network unplugged 1:36.444
Then the boot device has safe access rights 2.849
And Tails is running from USB drive "old" 0.339
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.076
And udev-watchdog is monitoring the correct device 0.258
And I unplug USB drive "old" 0.180
After features/support/hooks.rb:331 4.214
After features/support/hooks.rb:100 0.008
Tags: @product
2:3.895
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.165
And I start Tails from USB drive "old" with network unplugged and I login 1:24.652
Then Tails is running from USB drive "old" 0.293
And I create a persistent partition 29.099
And I take note of which tps features are available 1.279
Then a Tails persistence partition exists on USB drive "old" 0.792
And I shutdown Tails and wait for the computer to power off 7.612
After features/support/hooks.rb:331 0.616
After features/support/hooks.rb:100 0.009
Tags: @product
2:10.666
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.177
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:37.989
Then Tails is running from USB drive "old" 0.286
And all tps features are active 1.683
When I write some files expected to persist 1.527
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.172
And all persistence configuration files have safe access rights 0.372
And all persistent directories from the old Tails version have safe access rights 2.155
And I take note of which tps features are available 0.439
And I shutdown Tails and wait for the computer to power off 7.641
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.220
After features/support/hooks.rb:331 0.303
After features/support/hooks.rb:100 0.010
Tags: @product
2:35.433
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.309
And I log in to a new session 15.479
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.378
And I plug USB drive "to_upgrade" 2.402
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.705
Then the running Tails is installed on USB drive "to_upgrade" 20.657
And I unplug USB drive "to_upgrade" 0.265
And I unplug USB drive "__internal" 0.234
After features/support/hooks.rb:331 4.045
After features/support/hooks.rb:100 0.000
Tags: @product
1:45.156
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.216
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:36.057
Then all tps features from the old Tails version are active 1.566
And Tails is running from USB drive "to_upgrade" 0.345
And the boot device has safe access rights 3.333
And the expected persistent files created with the old Tails version are present in the filesystem 1.346
And all persistent directories from the old Tails version have safe access rights 2.290
After features/support/hooks.rb:331 0.736
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
4:54.486
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.203
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.278
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.277
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.456
When the network is plugged 0.095
And Tor is ready 14.122
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.658
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.909
Given I shutdown Tails and wait for the computer to power off 10.935
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:39.944
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 1.972
And the file system changes introduced in version 6.2~testoverlayfs are present 0.283
And only the 6.2~testoverlayfs SquashFS delta is installed 0.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.161
# 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.277
When the network is plugged 0.046
And Tor is ready 10.780
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.696
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.979
Given I shutdown Tails and wait for the computer to power off 8.038
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:38.174
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.134
And the file system changes introduced in version 6.3~testoverlayfs are present 0.476
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.139
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.285
When the network is plugged 0.057
And Tor is ready 11.226
Then the Upgrader considers the system as up-to-date 0.189
# 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 5.898
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.510
After features/support/hooks.rb:331 1.113
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
24.104
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 10.645
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.268
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the signing key used by the Upgrader is outdated 0.057
But a current signing key is available on our website 0.000
When the network is plugged 0.055
And Tor is ready 10.181
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.854
After features/support/hooks.rb:331 0.780
After features/support/hooks.rb:100 0.000