Project Number Date
test_Tails_ISO_stable 6033 03 Jan 2026, 11: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 10:56.668 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:10.321
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.054
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.151
When I start Tails from USB drive "old" with network unplugged 52.739
Then the boot device has safe access rights 2.644
And Tails is running from USB drive "old" 0.243
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.180
And I unplug USB drive "old" 0.143
After features/support/hooks.rb:331 3.794
After features/support/hooks.rb:100 0.012
Tags: @product
1:23.228
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.047
And I start Tails from USB drive "old" with network unplugged and I login 51.035
Then Tails is running from USB drive "old" 0.267
And I create a persistent partition 22.870
And I take note of which tps features are available 0.636
Then a Tails persistence partition exists on USB drive "old" 0.593
And I shutdown Tails and wait for the computer to power off 7.777
After features/support/hooks.rb:331 0.157
After features/support/hooks.rb:100 0.007
Tags: @product
1:21.376
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.050
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 56.712
Then Tails is running from USB drive "old" 0.246
And all tps features are active 1.033
When I write some files expected to persist 1.143
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.148
And all persistence configuration files have safe access rights 0.321
And all persistent directories from the old Tails version have safe access rights 1.849
And I take note of which tps features are available 0.143
And I shutdown Tails and wait for the computer to power off 8.195
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.531
After features/support/hooks.rb:331 0.452
After features/support/hooks.rb:100 0.006
Tags: @product
2:8.884
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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.006
And I log in to a new session 10.981
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.883
And I plug USB drive "to_upgrade" 2.321
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.923
Then the running Tails is installed on USB drive "to_upgrade" 15.501
And I unplug USB drive "to_upgrade" 0.135
And I unplug USB drive "__internal" 0.131
After features/support/hooks.rb:331 3.761
After features/support/hooks.rb:100 0.000
Tags: @product
1:4.460
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.057
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.130
Then all tps features from the old Tails version are active 1.009
And Tails is running from USB drive "to_upgrade" 0.219
And the boot device has safe access rights 2.351
And the expected persistent files created with the old Tails version are present in the filesystem 0.999
And all persistent directories from the old Tails version have safe access rights 1.692
After features/support/hooks.rb:331 0.793
After features/support/hooks.rb:100 0.006
3:29.457
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.455
And no SquashFS delta is installed 0.062
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.192
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.178
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.301
When the network is plugged 0.038
And Tor is ready 12.729
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.701
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.371
Given I shutdown Tails and wait for the computer to power off 9.235
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.749
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.056
And the file system changes introduced in version 6.2~testoverlayfs are present 0.239
And only the 6.2~testoverlayfs SquashFS delta is installed 0.043
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.132
# 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.215
When the network is plugged 0.015
And Tor is ready 10.815
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.424
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.121
Given I shutdown Tails and wait for the computer to power off 7.819
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.562
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.107
And the file system changes introduced in version 6.3~testoverlayfs are present 0.360
And only the 6.3~testoverlayfs SquashFS delta is installed 0.048
# 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.121
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.165
When the network is plugged 0.014
And Tor is ready 11.142
Then the Upgrader considers the system as up-to-date 10.533
# 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 4.117
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.335
After features/support/hooks.rb:331 0.902
After features/support/hooks.rb:100 0.012
18.939
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.366
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.192
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the signing key used by the Upgrader is outdated 0.038
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 8.309
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.975
After features/support/hooks.rb:331 0.813
After features/support/hooks.rb:100 0.000