Project Number Date
test_Tails_ISO_migrate-vms 3 07 Oct 2026, 03:41

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:45.156 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:18.926
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.086
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.845
When I start Tails from USB drive "old" with network unplugged 1:0.820
Then the boot device has safe access rights 2.443
And Tails is running from USB drive "old" 0.209
And there is no persistence partition on USB drive "old" 0.053
And process "udev-watchdog" is running 0.071
And udev-watchdog is monitoring the correct device 0.178
And I unplug USB drive "old" 0.173
After features/support/hooks.rb:339 1.424
After features/support/hooks.rb:108 0.008
Tags: @product
1:23.882
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.007
Given a computer 0.118
And I start Tails from USB drive "old" with network unplugged and I login 49.648
Then Tails is running from USB drive "old" 0.225
And I create a persistent partition 22.826
And I take note of which tps features are available 6.174
Then a Tails persistence partition exists on USB drive "old" 0.598
And I shutdown Tails and wait for the computer to power off 4.289
After features/support/hooks.rb:339 0.494
After features/support/hooks.rb:108 0.031
Tags: @product
1:39.941
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.010
Given a computer 0.139
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.538
Then Tails is running from USB drive "old" 0.204
And all tps features are active 8.858
When I write some files expected to persist 1.104
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.118
And all persistence configuration files have safe access rights 0.347
And all persistent directories from the old Tails version have safe access rights 1.832
And I take note of which tps features are available 6.635
And I shutdown Tails and wait for the computer to power off 5.231
# 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.932
After features/support/hooks.rb:339 0.440
After features/support/hooks.rb:108 0.006
Tags: @product
2:13.409
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.639
And I log in to a new session 11.263
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.779
And I plug USB drive "to_upgrade" 2.211
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.342
Then the running Tails is installed on USB drive "to_upgrade" 18.900
And I unplug USB drive "to_upgrade" 0.137
And I unplug USB drive "__internal" 0.132
After features/support/hooks.rb:339 1.849
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.621
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.112
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.315
Then all tps features from the old Tails version are active 1.256
And Tails is running from USB drive "to_upgrade" 0.237
And the boot device has safe access rights 2.531
And the expected persistent files created with the old Tails version are present in the filesystem 1.235
And all persistent directories from the old Tails version have safe access rights 1.931
After features/support/hooks.rb:339 0.574
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:37.251
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.535
And no SquashFS delta is installed 0.063
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.030
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.196
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.310
When the network is plugged 0.027
And Tor is ready 14.109
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.322
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.246
Given I shutdown Tails and wait for the computer to power off 5.573
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.027
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 8.227
And the file system changes introduced in version 6.2~testoverlayfs are present 0.193
And only the 6.2~testoverlayfs SquashFS delta is installed 0.048
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.121
# 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.163
When the network is plugged 0.038
And Tor is ready 10.797
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.934
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.488
Given I shutdown Tails and wait for the computer to power off 2.639
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.770
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.092
And the file system changes introduced in version 6.3~testoverlayfs are present 0.269
And only the 6.3~testoverlayfs SquashFS delta is installed 0.049
# 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.109
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.211
When the network is plugged 0.026
And Tor is ready 10.784
Then the Upgrader considers the system as up-to-date 0.115
# 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 4.146
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.306
After features/support/hooks.rb:339 0.672
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
20.123
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 with a persistent partition enabled and logged in 8.269
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.318
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.030
And the signing key used by the Upgrader is outdated 0.058
But a current signing key is available on our website 0.000
When the network is plugged 0.044
And Tor is ready 9.940
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.461
After features/support/hooks.rb:339 0.591
After features/support/hooks.rb:108 0.000