Project Number Date
test_Tails_ISO_devel 4580 01 Sep 2026, 07:37

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:31.032 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:10.903
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.087
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.594
When I start Tails from USB drive "old" with network unplugged 53.250
Then the boot device has safe access rights 2.253
And Tails is running from USB drive "old" 0.254
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.064
And udev-watchdog is monitoring the correct device 0.183
And I unplug USB drive "old" 0.120
After features/support/hooks.rb:339 3.725
After features/support/hooks.rb:108 0.030
Tags: @product
1:24.325
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.103
And I start Tails from USB drive "old" with network unplugged and I login 48.692
Then Tails is running from USB drive "old" 0.268
And I create a persistent partition 23.959
And I take note of which tps features are available 6.788
Then a Tails persistence partition exists on USB drive "old" 0.523
And I shutdown Tails and wait for the computer to power off 3.989
After features/support/hooks.rb:339 0.540
After features/support/hooks.rb:108 0.006
Tags: @product
1:36.757
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.098
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.170
Then Tails is running from USB drive "old" 0.309
And all tps features are active 9.651
When I write some files expected to persist 1.122
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.128
And all persistence configuration files have safe access rights 0.223
And all persistent directories from the old Tails version have safe access rights 1.612
And I take note of which tps features are available 5.936
And I shutdown Tails and wait for the computer to power off 4.093
# 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.410
After features/support/hooks.rb:339 0.608
After features/support/hooks.rb:108 0.005
Tags: @product
2:13.533
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.262
And I log in to a new session 12.303
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.820
And I plug USB drive "to_upgrade" 2.191
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.499
Then the running Tails is installed on USB drive "to_upgrade" 18.154
And I unplug USB drive "to_upgrade" 0.150
And I unplug USB drive "__internal" 0.150
After features/support/hooks.rb:339 1.534
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.255
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.075
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.101
Then all tps features from the old Tails version are active 1.088
And Tails is running from USB drive "to_upgrade" 0.229
And the boot device has safe access rights 2.506
And the expected persistent files created with the old Tails version are present in the filesystem 1.278
And all persistent directories from the old Tails version have safe access rights 1.974
After features/support/hooks.rb:339 0.941
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:36.079
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.845
And no SquashFS delta is installed 0.068
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.230
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.209
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.312
When the network is plugged 0.024
And Tor is ready 13.679
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.490
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.854
Given I shutdown Tails and wait for the computer to power off 5.327
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.974
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.242
And the file system changes introduced in version 6.2~testoverlayfs are present 0.169
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.110
# 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.189
When the network is plugged 0.032
And Tor is ready 10.508
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.609
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.674
Given I shutdown Tails and wait for the computer to power off 4.005
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.724
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.041
And the file system changes introduced in version 6.3~testoverlayfs are present 0.372
And only the 6.3~testoverlayfs SquashFS delta is installed 0.056
# 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.114
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.185
When the network is plugged 0.035
And Tor is ready 10.277
Then the Upgrader considers the system as up-to-date 0.103
# 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.206
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.311
After features/support/hooks.rb:339 0.888
After features/support/hooks.rb:108 0.030
Tags: @product @automatic_upgrade
19.178
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.261
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.238
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.054
But a current signing key is available on our website 0.000
When the network is plugged 0.034
And Tor is ready 9.565
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.973
After features/support/hooks.rb:339 0.959
After features/support/hooks.rb:108 0.000