Project Number Date
test_Tails_ISO_stable 6310 20 Apr 2026, 13:58

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 13:30.171 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:15.595
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.083
And I create a 7200 MiB disk named "old" 0.013
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 14.871
When I start Tails from USB drive "old" with network unplugged 55.694
Then the boot device has safe access rights 3.203
And Tails is running from USB drive "old" 0.241
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.061
And udev-watchdog is monitoring the correct device 0.219
And I unplug USB drive "old" 0.138
After features/support/hooks.rb:331 1.256
After features/support/hooks.rb:100 0.008
Tags: @product
1:37.902
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.068
And I start Tails from USB drive "old" with network unplugged and I login 1:0.486
Then Tails is running from USB drive "old" 0.325
And I create a persistent partition 28.199
And I take note of which tps features are available 1.000
Then a Tails persistence partition exists on USB drive "old" 0.653
And I shutdown Tails and wait for the computer to power off 7.168
After features/support/hooks.rb:331 0.501
After features/support/hooks.rb:100 0.007
Tags: @product
1:33.933
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.067
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:8.988
Then Tails is running from USB drive "old" 0.416
And all tps features are active 1.606
When I write some files expected to persist 1.650
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.226
And all persistence configuration files have safe access rights 0.530
And all persistent directories from the old Tails version have safe access rights 2.465
And I take note of which tps features are available 0.194
And I shutdown Tails and wait for the computer to power off 4.315
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.471
After features/support/hooks.rb:331 0.432
After features/support/hooks.rb:100 0.062
Tags: @product
2:21.657
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.016
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.430
And I log in to a new session 16.749
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.880
And I plug USB drive "to_upgrade" 2.229
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.902
Then the running Tails is installed on USB drive "to_upgrade" 19.106
And I unplug USB drive "to_upgrade" 0.162
And I unplug USB drive "__internal" 0.196
After features/support/hooks.rb:331 3.604
After features/support/hooks.rb:100 0.000
Tags: @product
1:20.336
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.068
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:11.590
Then all tps features from the old Tails version are active 1.198
And Tails is running from USB drive "to_upgrade" 0.312
And the boot device has safe access rights 3.446
And the expected persistent files created with the old Tails version are present in the filesystem 1.383
And all persistent directories from the old Tails version have safe access rights 2.334
After features/support/hooks.rb:331 1.025
After features/support/hooks.rb:100 0.006
4:53.882
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 8.513
And no SquashFS delta is installed 0.146
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.404
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.228
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.397
When the network is plugged 0.059
And Tor is ready 27.207
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.461
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.789
Given I shutdown Tails and wait for the computer to power off 21.315
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.730
Then Tails is running version 6.2~testoverlayfs 0.009
And all tps features are active 1.285
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.050
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.151
# 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.223
When the network is plugged 0.016
And Tor is ready 24.691
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.415
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.216
Given I shutdown Tails and wait for the computer to power off 12.401
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.220
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.341
And the file system changes introduced in version 6.3~testoverlayfs are present 0.442
And only the 6.3~testoverlayfs SquashFS delta is installed 0.080
# 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.194
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.286
When the network is plugged 0.032
And Tor is ready 23.775
Then the Upgrader considers the system as up-to-date 0.114
# 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.763
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.556
After features/support/hooks.rb:331 1.121
After features/support/hooks.rb:100 0.013
26.864
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 7.796
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.284
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.093
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 18.218
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.387
After features/support/hooks.rb:331 1.135
After features/support/hooks.rb:100 0.000