Project Number Date
test_Tails_ISO_stable 6586 17 Aug 2026, 17:59

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 11:46.685 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:16.165
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.098
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.029
And I write an old version of the Tails USB image to disk "old" 14.428
When I start Tails from USB drive "old" with network unplugged 57.545
Then the boot device has safe access rights 2.447
And Tails is running from USB drive "old" 0.223
And there is no persistence partition on USB drive "old" 0.034
And process "udev-watchdog" is running 0.034
And udev-watchdog is monitoring the correct device 0.174
And I unplug USB drive "old" 0.126
After features/support/hooks.rb:339 3.381
After features/support/hooks.rb:108 0.053
Tags: @product
1:23.905
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.072
And I start Tails from USB drive "old" with network unplugged and I login 48.258
Then Tails is running from USB drive "old" 0.251
And I create a persistent partition 23.971
And I take note of which tps features are available 6.735
Then a Tails persistence partition exists on USB drive "old" 0.531
And I shutdown Tails and wait for the computer to power off 4.084
After features/support/hooks.rb:339 0.400
After features/support/hooks.rb:108 0.006
Tags: @product
1:34.382
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.086
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.710
Then Tails is running from USB drive "old" 0.264
And all tps features are active 7.891
When I write some files expected to persist 1.024
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.133
And all persistence configuration files have safe access rights 0.314
And all persistent directories from the old Tails version have safe access rights 1.600
And I take note of which tps features are available 5.770
And I shutdown Tails and wait for the computer to power off 2.573
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 12.013
After features/support/hooks.rb:339 0.424
After features/support/hooks.rb:108 0.005
Tags: @product
2:14.619
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.355
And I log in to a new session 12.842
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.650
And I plug USB drive "to_upgrade" 2.244
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.704
Then the running Tails is installed on USB drive "to_upgrade" 18.574
And I unplug USB drive "to_upgrade" 0.134
And I unplug USB drive "__internal" 0.113
After features/support/hooks.rb:339 3.716
After features/support/hooks.rb:108 0.000
Tags: @product
1:8.911
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.008
Given a computer 0.663
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.084
Then all tps features from the old Tails version are active 0.959
And Tails is running from USB drive "to_upgrade" 0.200
And the boot device has safe access rights 2.234
And the expected persistent files created with the old Tails version are present in the filesystem 0.985
And all persistent directories from the old Tails version have safe access rights 1.783
After features/support/hooks.rb:339 0.796
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
3:48.317
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.815
And no SquashFS delta is installed 0.064
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.203
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.208
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.346
When the network is plugged 0.031
And Tor is ready 13.579
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.039
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.032
Given I shutdown Tails and wait for the computer to power off 5.335
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.635
Then Tails is running version 6.2~testoverlayfs 0.009
And all tps features are active 8.143
And the file system changes introduced in version 6.2~testoverlayfs are present 0.240
And only the 6.2~testoverlayfs SquashFS delta is installed 0.041
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.120
# 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.204
When the network is plugged 0.029
And Tor is ready 10.589
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.576
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.715
Given I shutdown Tails and wait for the computer to power off 4.065
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.401
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.173
And the file system changes introduced in version 6.3~testoverlayfs are present 0.387
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.102
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.250
When the network is plugged 0.052
And Tor is ready 10.397
Then the Upgrader considers the system as up-to-date 10.427
# 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 3.694
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.290
After features/support/hooks.rb:339 0.571
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
20.383
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.884
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.224
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 0.048
But a current signing key is available on our website 0.000
When the network is plugged 0.024
And Tor is ready 10.625
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.527
After features/support/hooks.rb:339 0.806
After features/support/hooks.rb:108 0.000