Project Number Date
test_Tails_ISO_21322-tails-testers-migration 1 27 Aug 2026, 12:31

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.964 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:8.290
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.100
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 13.909
When I start Tails from USB drive "old" with network unplugged 50.220
Then the boot device has safe access rights 2.413
And Tails is running from USB drive "old" 0.197
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.067
And udev-watchdog is monitoring the correct device 0.177
And I unplug USB drive "old" 0.115
After features/support/hooks.rb:339 3.976
After features/support/hooks.rb:108 0.013
Tags: @product
1:24.939
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.103
And I start Tails from USB drive "old" with network unplugged and I login 49.389
Then Tails is running from USB drive "old" 0.236
And I create a persistent partition 23.530
And I take note of which tps features are available 7.023
Then a Tails persistence partition exists on USB drive "old" 0.591
And I shutdown Tails and wait for the computer to power off 4.063
After features/support/hooks.rb:339 0.386
After features/support/hooks.rb:108 0.007
Tags: @product
1:38.787
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.140
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.893
Then Tails is running from USB drive "old" 0.239
And all tps features are active 7.695
When I write some files expected to persist 1.310
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.173
And all persistence configuration files have safe access rights 0.300
And all persistent directories from the old Tails version have safe access rights 2.176
And I take note of which tps features are available 6.957
And I shutdown Tails and wait for the computer to power off 4.140
# 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.760
After features/support/hooks.rb:339 0.557
After features/support/hooks.rb:108 0.006
Tags: @product
2:19.280
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 without a persistent partition and stopped at Tails Greeter's login screen 9.928
And I log in to a new session 14.949
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.771
And I plug USB drive "to_upgrade" 2.198
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.916
Then the running Tails is installed on USB drive "to_upgrade" 19.116
And I unplug USB drive "to_upgrade" 0.172
And I unplug USB drive "__internal" 0.225
After features/support/hooks.rb:339 3.824
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.839
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 "to_upgrade" with network unplugged and I login with persistence enabled 1:4.255
Then all tps features from the old Tails version are active 1.090
And Tails is running from USB drive "to_upgrade" 0.216
And the boot device has safe access rights 2.315
And the expected persistent files created with the old Tails version are present in the filesystem 1.108
And all persistent directories from the old Tails version have safe access rights 1.755
After features/support/hooks.rb:339 0.925
After features/support/hooks.rb:108 0.019
Tags: @product @automatic_upgrade
3:43.537
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.473
And no SquashFS delta is installed 0.079
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.235
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.277
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.316
When the network is plugged 0.031
And Tor is ready 13.562
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.435
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.157
Given I shutdown Tails and wait for the computer to power off 5.283
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.099
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.039
And the file system changes introduced in version 6.2~testoverlayfs are present 0.255
And only the 6.2~testoverlayfs SquashFS delta is installed 0.039
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.136
# 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.183
When the network is plugged 0.026
And Tor is ready 15.592
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.329
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.765
Given I shutdown Tails and wait for the computer to power off 4.032
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.726
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 9.420
And the file system changes introduced in version 6.3~testoverlayfs are present 0.400
And only the 6.3~testoverlayfs SquashFS delta is installed 0.035
# 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.116
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.158
When the network is plugged 0.042
And Tor is ready 10.771
Then the Upgrader considers the system as up-to-date 0.139
# 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.914
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.395
After features/support/hooks.rb:339 0.930
After features/support/hooks.rb:108 0.018
Tags: @product @automatic_upgrade
19.289
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.182
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.205
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the signing key used by the Upgrader is outdated 0.049
But a current signing key is available on our website 0.000
When the network is plugged 0.024
And Tor is ready 9.761
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.018
After features/support/hooks.rb:339 0.939
After features/support/hooks.rb:108 0.000