Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 77 29 Jun 2026, 14:53

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 12:51.283 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:17.774
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given a computer 0.108
And I create a 7200 MiB disk named "old" 0.017
And I plug USB drive "old" 1.029
And I write an old version of the Tails USB image to disk "old" 14.130
When I start Tails from USB drive "old" with network unplugged 58.112
Then the boot device has safe access rights 3.528
And Tails is running from USB drive "old" 0.296
And there is no persistence partition on USB drive "old" 0.052
And process "udev-watchdog" is running 0.074
And udev-watchdog is monitoring the correct device 0.268
And I unplug USB drive "old" 0.153
After features/support/hooks.rb:339 1.884
After features/support/hooks.rb:108 0.041
Tags: @product
1:38.601
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.016
Given a computer 0.268
And I start Tails from USB drive "old" with network unplugged and I login 59.153
Then Tails is running from USB drive "old" 0.296
And I create a persistent partition 25.663
And I take note of which tps features are available 4.357
Then a Tails persistence partition exists on USB drive "old" 0.599
And I shutdown Tails and wait for the computer to power off 8.261
After features/support/hooks.rb:339 0.431
After features/support/hooks.rb:108 0.007
Tags: @product
1:46.180
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.086
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:12.575
Then Tails is running from USB drive "old" 0.288
And all tps features are active 5.968
When I write some files expected to persist 1.427
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.184
And all persistence configuration files have safe access rights 0.340
And all persistent directories from the old Tails version have safe access rights 2.464
And I take note of which tps features are available 4.904
And I shutdown Tails and wait for the computer to power off 4.079
# 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" 13.861
After features/support/hooks.rb:339 0.193
After features/support/hooks.rb:108 0.006
Tags: @product
2:16.801
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 without a persistent partition and stopped at Tails Greeter's login screen 8.421
And I log in to a new session 14.383
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.859
And I plug USB drive "to_upgrade" 2.231
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.369
Then the running Tails is installed on USB drive "to_upgrade" 17.214
And I unplug USB drive "to_upgrade" 0.142
And I unplug USB drive "__internal" 0.177
After features/support/hooks.rb:339 2.661
After features/support/hooks.rb:108 0.000
Tags: @product
1:19.043
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.010
Given a computer 0.124
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:10.546
Then all tps features from the old Tails version are active 1.491
And Tails is running from USB drive "to_upgrade" 0.311
And the boot device has safe access rights 3.064
And the expected persistent files created with the old Tails version are present in the filesystem 1.283
And all persistent directories from the old Tails version have safe access rights 2.220
After features/support/hooks.rb:339 0.934
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
4:11.769
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.198
And no SquashFS delta is installed 0.080
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.218
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.246
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.361
When the network is plugged 0.016
And Tor is ready 12.959
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.442
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.390
Given I shutdown Tails and wait for the computer to power off 7.194
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.769
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 5.665
And the file system changes introduced in version 6.2~testoverlayfs are present 0.234
And only the 6.2~testoverlayfs SquashFS delta is installed 0.054
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.155
# 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.280
When the network is plugged 0.016
And Tor is ready 10.859
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.835
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.223
Given I shutdown Tails and wait for the computer to power off 8.449
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.373
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 5.208
And the file system changes introduced in version 6.3~testoverlayfs are present 0.360
And only the 6.3~testoverlayfs SquashFS delta is installed 0.048
# 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.112
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.210
When the network is plugged 0.014
And Tor is ready 10.506
Then the Upgrader considers the system as up-to-date 10.598
# 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.812
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.789
After features/support/hooks.rb:339 0.721
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
21.113
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.119
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.417
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
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.021
And Tor is ready 9.906
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.525
After features/support/hooks.rb:339 0.696
After features/support/hooks.rb:108 0.000