Project Number Date
test_Tails_ISO_21322-tails-testers-migration 2 28 Aug 2026, 05:04

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:10.457 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:3.723
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.074
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.030
And I write an old version of the Tails USB image to disk "old" 13.121
When I start Tails from USB drive "old" with network unplugged 46.549
Then the boot device has safe access rights 2.243
And Tails is running from USB drive "old" 0.211
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.041
And udev-watchdog is monitoring the correct device 0.223
And I unplug USB drive "old" 0.156
After features/support/hooks.rb:339 1.537
After features/support/hooks.rb:108 0.006
Tags: @product
1:24.355
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.081
And I start Tails from USB drive "old" with network unplugged and I login 49.419
Then Tails is running from USB drive "old" 0.253
And I create a persistent partition 23.520
And I take note of which tps features are available 6.538
Then a Tails persistence partition exists on USB drive "old" 0.463
And I shutdown Tails and wait for the computer to power off 4.079
After features/support/hooks.rb:339 0.482
After features/support/hooks.rb:108 0.006
Tags: @product
1:33.219
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.087
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.775
Then Tails is running from USB drive "old" 0.211
And all tps features are active 6.958
When I write some files expected to persist 1.326
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.139
And all persistence configuration files have safe access rights 0.312
And all persistent directories from the old Tails version have safe access rights 1.936
And I take note of which tps features are available 6.484
And I shutdown Tails and wait for the computer to power off 2.564
# 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.421
After features/support/hooks.rb:339 0.587
After features/support/hooks.rb:108 0.006
Tags: @product
2:13.355
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.257
And I log in to a new session 12.504
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.707
And I plug USB drive "to_upgrade" 2.206
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.153
Then the running Tails is installed on USB drive "to_upgrade" 18.284
And I unplug USB drive "to_upgrade" 0.114
And I unplug USB drive "__internal" 0.127
After features/support/hooks.rb:339 3.790
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.116
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.078
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.609
Then all tps features from the old Tails version are active 1.105
And Tails is running from USB drive "to_upgrade" 0.263
And the boot device has safe access rights 2.231
And the expected persistent files created with the old Tails version are present in the filesystem 1.117
And all persistent directories from the old Tails version have safe access rights 1.711
After features/support/hooks.rb:339 0.519
After features/support/hooks.rb:108 0.008
Tags: @product @automatic_upgrade
3:27.092
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.977
And no SquashFS delta is installed 0.077
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.172
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.178
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.248
When the network is plugged 0.025
And Tor is ready 11.989
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.397
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.882
Given I shutdown Tails and wait for the computer to power off 5.302
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.825
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 7.723
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.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.109
# 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.031
And Tor is ready 10.300
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.473
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.733
Given I shutdown Tails and wait for the computer to power off 3.918
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.688
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.134
And the file system changes introduced in version 6.3~testoverlayfs are present 0.393
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.117
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.163
When the network is plugged 0.033
And Tor is ready 10.734
Then the Upgrader considers the system as up-to-date 0.102
# 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.479
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.813
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
19.595
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 Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.225
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.061
But a current signing key is available on our website 0.000
When the network is plugged 0.032
And Tor is ready 9.034
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.073
After features/support/hooks.rb:339 0.586
After features/support/hooks.rb:108 0.000