Project Number Date
test_Tails_ISO_stable 6619 01 Sep 2026, 11:39

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:44.701 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.725
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.112
And I create a 7200 MiB disk named "old" 0.024
And I plug USB drive "old" 1.024
And I write an old version of the Tails USB image to disk "old" 14.368
When I start Tails from USB drive "old" with network unplugged 51.122
Then the boot device has safe access rights 2.423
And Tails is running from USB drive "old" 0.227
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.048
And udev-watchdog is monitoring the correct device 0.161
And I unplug USB drive "old" 0.153
After features/support/hooks.rb:339 1.618
After features/support/hooks.rb:108 0.007
Tags: @product
1:23.623
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.089
And I start Tails from USB drive "old" with network unplugged and I login 49.572
Then Tails is running from USB drive "old" 0.194
And I create a persistent partition 23.449
And I take note of which tps features are available 7.068
Then a Tails persistence partition exists on USB drive "old" 0.617
And I shutdown Tails and wait for the computer to power off 2.632
After features/support/hooks.rb:339 0.217
After features/support/hooks.rb:108 0.006
Tags: @product
1:36.528
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.085
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.606
Then Tails is running from USB drive "old" 0.220
And all tps features are active 8.079
When I write some files expected to persist 1.417
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.190
And all persistence configuration files have safe access rights 0.307
And all persistent directories from the old Tails version have safe access rights 1.756
And I take note of which tps features are available 6.189
And I shutdown Tails and wait for the computer to power off 2.531
# 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" 12.144
After features/support/hooks.rb:339 0.345
After features/support/hooks.rb:108 0.013
Tags: @product
2:13.573
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 without a persistent partition and stopped at Tails Greeter's login screen 8.699
And I log in to a new session 11.169
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.745
And I plug USB drive "to_upgrade" 2.243
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.925
Then the running Tails is installed on USB drive "to_upgrade" 18.518
And I unplug USB drive "to_upgrade" 0.139
And I unplug USB drive "__internal" 0.131
After features/support/hooks.rb:339 3.530
After features/support/hooks.rb:108 0.000
Tags: @product
1:16.111
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.007
Given a computer 0.111
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.961
Then all tps features from the old Tails version are active 1.276
And Tails is running from USB drive "to_upgrade" 0.229
And the boot device has safe access rights 2.290
And the expected persistent files created with the old Tails version are present in the filesystem 1.016
And all persistent directories from the old Tails version have safe access rights 2.225
After features/support/hooks.rb:339 0.529
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
3:44.783
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.982
And no SquashFS delta is installed 0.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.219
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.094
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.306
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.412
When the network is plugged 0.039
And Tor is ready 13.557
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.340
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.608
Given I shutdown Tails and wait for the computer to power off 5.282
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.960
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 8.284
And the file system changes introduced in version 6.2~testoverlayfs are present 0.163
And only the 6.2~testoverlayfs SquashFS delta is installed 0.041
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.126
# 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.166
When the network is plugged 0.036
And Tor is ready 10.915
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.892
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.089
Given I shutdown Tails and wait for the computer to power off 2.593
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.155
Then Tails is running version 6.3~testoverlayfs 0.009
And all tps features are active 8.262
And the file system changes introduced in version 6.3~testoverlayfs are present 0.374
And only the 6.3~testoverlayfs SquashFS delta is installed 0.045
# 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.092
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.257
When the network is plugged 0.027
And Tor is ready 10.851
Then the Upgrader considers the system as up-to-date 10.509
# 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.690
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.309
After features/support/hooks.rb:339 1.072
After features/support/hooks.rb:108 0.013
Tags: @product @automatic_upgrade
20.355
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 with a persistent partition enabled and logged in 8.028
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.215
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.027
And Tor is ready 10.164
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.833
After features/support/hooks.rb:339 0.823
After features/support/hooks.rb:108 0.000