Project Number Date
test_Tails_ISO_stable 6671 16 Sep 2026, 07:23

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:39.292 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
56.672
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.085
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.024
And I write an old version of the Tails USB image to disk "old" 13.351
When I start Tails from USB drive "old" with network unplugged 39.825
Then the boot device has safe access rights 1.783
And Tails is running from USB drive "old" 0.205
And there is no persistence partition on USB drive "old" 0.039
And process "udev-watchdog" is running 0.041
And udev-watchdog is monitoring the correct device 0.176
And I unplug USB drive "old" 0.118
After features/support/hooks.rb:339 1.571
After features/support/hooks.rb:108 0.005
Tags: @product
1:18.017
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.078
And I start Tails from USB drive "old" with network unplugged and I login 46.230
Then Tails is running from USB drive "old" 0.230
And I create a persistent partition 22.708
And I take note of which tps features are available 5.723
Then a Tails persistence partition exists on USB drive "old" 0.518
And I shutdown Tails and wait for the computer to power off 2.528
After features/support/hooks.rb:339 0.281
After features/support/hooks.rb:108 0.005
Tags: @product
1:27.094
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.168
Then Tails is running from USB drive "old" 0.163
And all tps features are active 6.554
When I write some files expected to persist 0.915
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.099
And all persistence configuration files have safe access rights 0.190
And all persistent directories from the old Tails version have safe access rights 1.304
And I take note of which tps features are available 6.048
And I shutdown Tails and wait for the computer to power off 2.551
# 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.015
After features/support/hooks.rb:339 0.169
After features/support/hooks.rb:108 0.006
Tags: @product
2:10.210
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.472
And I log in to a new session 10.849
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.604
And I plug USB drive "to_upgrade" 2.275
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.377
Then the running Tails is installed on USB drive "to_upgrade" 17.386
And I unplug USB drive "to_upgrade" 0.132
And I unplug USB drive "__internal" 0.112
After features/support/hooks.rb:339 1.634
After features/support/hooks.rb:108 0.000
Tags: @product
1:6.151
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.071
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.780
Then all tps features from the old Tails version are active 0.908
And Tails is running from USB drive "to_upgrade" 0.199
And the boot device has safe access rights 1.769
And the expected persistent files created with the old Tails version are present in the filesystem 0.872
And all persistent directories from the old Tails version have safe access rights 1.549
After features/support/hooks.rb:339 0.554
After features/support/hooks.rb:108 0.018
3:22.524
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.125
And no SquashFS delta is installed 0.047
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.165
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.233
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.289
When the network is plugged 0.034
And Tor is ready 11.343
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.120
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.791
Given I shutdown Tails and wait for the computer to power off 5.269
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.752
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 7.463
And the file system changes introduced in version 6.2~testoverlayfs are present 0.146
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.099
# 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.151
When the network is plugged 0.027
And Tor is ready 10.249
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.886
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.378
Given I shutdown Tails and wait for the computer to power off 2.580
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.386
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 7.388
And the file system changes introduced in version 6.3~testoverlayfs are present 0.292
And only the 6.3~testoverlayfs SquashFS delta is installed 0.040
# 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.077
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.159
When the network is plugged 0.031
And Tor is ready 11.052
Then the Upgrader considers the system as up-to-date 0.073
# 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.461
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.282
After features/support/hooks.rb:339 0.784
After features/support/hooks.rb:108 0.009
18.621
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.854
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.260
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.039
But a current signing key is available on our website 0.000
When the network is plugged 0.033
And Tor is ready 8.848
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.542
After features/support/hooks.rb:339 0.541
After features/support/hooks.rb:108 0.000