Project Number Date
test_Tails_ISO_devel 4555 18 Aug 2026, 07: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 11:0.454 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:9.177
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.108
And I create a 7200 MiB disk named "old" 0.023
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 12.970
When I start Tails from USB drive "old" with network unplugged 52.647
Then the boot device has safe access rights 1.872
And Tails is running from USB drive "old" 0.186
And there is no persistence partition on USB drive "old" 0.051
And process "udev-watchdog" is running 0.049
And udev-watchdog is monitoring the correct device 0.134
And I unplug USB drive "old" 0.110
After features/support/hooks.rb:339 3.375
After features/support/hooks.rb:108 0.015
Tags: @product
1:17.137
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.070
And I start Tails from USB drive "old" with network unplugged and I login 45.935
Then Tails is running from USB drive "old" 0.227
And I create a persistent partition 22.019
And I take note of which tps features are available 5.748
Then a Tails persistence partition exists on USB drive "old" 0.529
And I shutdown Tails and wait for the computer to power off 2.608
After features/support/hooks.rb:339 0.164
After features/support/hooks.rb:108 0.005
Tags: @product
1:27.818
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.076
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.894
Then Tails is running from USB drive "old" 0.208
And all tps features are active 7.211
When I write some files expected to persist 1.069
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.152
And all persistence configuration files have safe access rights 0.259
And all persistent directories from the old Tails version have safe access rights 1.602
And I take note of which tps features are available 5.790
And I shutdown Tails and wait for the computer to power off 2.558
# 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" 10.995
After features/support/hooks.rb:339 0.446
After features/support/hooks.rb:108 0.006
Tags: @product
2:9.505
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 7.928
And I log in to a new session 11.611
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.561
And I plug USB drive "to_upgrade" 2.222
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.283
Then the running Tails is installed on USB drive "to_upgrade" 16.653
And I unplug USB drive "to_upgrade" 0.122
And I unplug USB drive "__internal" 0.120
After features/support/hooks.rb:339 1.565
After features/support/hooks.rb:108 0.000
Tags: @product
1:4.668
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.076
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.073
Then all tps features from the old Tails version are active 1.004
And Tails is running from USB drive "to_upgrade" 0.168
And the boot device has safe access rights 1.822
And the expected persistent files created with the old Tails version are present in the filesystem 1.010
And all persistent directories from the old Tails version have safe access rights 1.512
After features/support/hooks.rb:339 0.487
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:34.177
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 8.155
And no SquashFS delta is installed 0.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.193
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.204
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.237
When the network is plugged 0.025
And Tor is ready 12.834
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.482
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.866
Given I shutdown Tails and wait for the computer to power off 5.218
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.026
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.288
And the file system changes introduced in version 6.2~testoverlayfs are present 0.138
And only the 6.2~testoverlayfs SquashFS delta is installed 0.050
# 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.172
When the network is plugged 0.025
And Tor is ready 10.466
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.385
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.614
Given I shutdown Tails and wait for the computer to power off 3.963
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.353
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.367
And the file system changes introduced in version 6.3~testoverlayfs are present 0.275
And only the 6.3~testoverlayfs SquashFS delta is installed 0.035
# 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.099
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.140
When the network is plugged 0.030
And Tor is ready 10.620
Then the Upgrader considers the system as up-to-date 10.357
# 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.032
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.268
After features/support/hooks.rb:339 0.548
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
17.968
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.822
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.228
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the signing key used by the Upgrader is outdated 0.039
But a current signing key is available on our website 0.000
When the network is plugged 0.032
And Tor is ready 7.843
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.963
After features/support/hooks.rb:339 0.740
After features/support/hooks.rb:108 0.000