Project Number Date
test_Tails_ISO_devel 4590 03 Sep 2026, 14:27

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:42.651 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:4.208
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.094
And I create a 7200 MiB disk named "old" 0.023
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 16.629
When I start Tails from USB drive "old" with network unplugged 43.467
Then the boot device has safe access rights 2.344
And Tails is running from USB drive "old" 0.224
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.142
And I unplug USB drive "old" 0.148
After features/support/hooks.rb:339 1.163
After features/support/hooks.rb:108 0.006
Tags: @product
1:25.066
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.085
And I start Tails from USB drive "old" with network unplugged and I login 49.513
Then Tails is running from USB drive "old" 0.508
And I create a persistent partition 24.025
And I take note of which tps features are available 6.264
Then a Tails persistence partition exists on USB drive "old" 0.508
And I shutdown Tails and wait for the computer to power off 4.160
After features/support/hooks.rb:339 0.312
After features/support/hooks.rb:108 0.014
Tags: @product
1:34.295
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.010
Given a computer 0.096
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.990
Then Tails is running from USB drive "old" 0.217
And all tps features are active 7.180
When I write some files expected to persist 1.220
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.159
And all persistence configuration files have safe access rights 0.242
And all persistent directories from the old Tails version have safe access rights 1.798
And I take note of which tps features are available 6.794
And I shutdown Tails and wait for the computer to power off 2.667
# 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" 11.924
After features/support/hooks.rb:339 0.548
After features/support/hooks.rb:108 0.014
Tags: @product
2:14.374
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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 8.868
And I log in to a new session 11.842
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.627
And I plug USB drive "to_upgrade" 2.232
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.550
Then the running Tails is installed on USB drive "to_upgrade" 19.011
And I unplug USB drive "to_upgrade" 0.124
And I unplug USB drive "__internal" 0.118
After features/support/hooks.rb:339 1.593
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.441
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 1:4.101
Then all tps features from the old Tails version are active 1.250
And Tails is running from USB drive "to_upgrade" 0.207
And the boot device has safe access rights 2.796
And the expected persistent files created with the old Tails version are present in the filesystem 1.111
And all persistent directories from the old Tails version have safe access rights 1.897
After features/support/hooks.rb:339 0.790
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
3:53.026
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.721
And no SquashFS delta is installed 0.067
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.239
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.224
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.361
When the network is plugged 0.023
And Tor is ready 13.680
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.277
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.454
Given I shutdown Tails and wait for the computer to power off 7.075
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.883
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.401
And the file system changes introduced in version 6.2~testoverlayfs are present 0.254
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.173
# 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.268
When the network is plugged 0.023
And Tor is ready 10.669
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.861
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.566
Given I shutdown Tails and wait for the computer to power off 4.273
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.807
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 8.118
And the file system changes introduced in version 6.3~testoverlayfs are present 0.288
And only the 6.3~testoverlayfs SquashFS delta is installed 0.036
# 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.076
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.177
When the network is plugged 0.027
And Tor is ready 10.545
Then the Upgrader considers the system as up-to-date 10.471
# 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.534
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.308
After features/support/hooks.rb:339 0.929
After features/support/hooks.rb:108 0.050
Tags: @product @automatic_upgrade
20.237
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.512
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.231
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.050
But a current signing key is available on our website 0.000
When the network is plugged 0.028
And Tor is ready 8.580
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.792
After features/support/hooks.rb:339 1.015
After features/support/hooks.rb:108 0.000