Project Number Date
test_Tails_ISO_21565-flatpak-safe 85 12 Oct 2026, 03:26

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:15.340 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:5.645
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.032
And I plug USB drive "old" 1.034
And I write an old version of the Tails USB image to disk "old" 13.830
When I start Tails from USB drive "old" with network unplugged 47.564
Then the boot device has safe access rights 2.396
And Tails is running from USB drive "old" 0.264
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.055
And udev-watchdog is monitoring the correct device 0.211
And I unplug USB drive "old" 0.121
After features/support/hooks.rb:339 3.477
After features/support/hooks.rb:108 0.011
Tags: @product
1:24.788
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.129
And I start Tails from USB drive "old" with network unplugged and I login 49.791
Then Tails is running from USB drive "old" 0.191
And I create a persistent partition 23.310
And I take note of which tps features are available 6.732
Then a Tails persistence partition exists on USB drive "old" 0.546
And I shutdown Tails and wait for the computer to power off 4.087
After features/support/hooks.rb:339 0.520
After features/support/hooks.rb:108 0.006
Tags: @product
1:32.310
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.097
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.391
Then Tails is running from USB drive "old" 0.212
And all tps features are active 6.713
When I write some files expected to persist 1.022
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.133
And all persistence configuration files have safe access rights 0.358
And all persistent directories from the old Tails version have safe access rights 2.014
And I take note of which tps features are available 6.130
And I shutdown Tails and wait for the computer to power off 2.593
# 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.641
After features/support/hooks.rb:339 0.489
After features/support/hooks.rb:108 0.005
Tags: @product
2:14.010
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.798
And I log in to a new session 11.635
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.677
And I plug USB drive "to_upgrade" 2.241
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.947
Then the running Tails is installed on USB drive "to_upgrade" 18.457
And I unplug USB drive "to_upgrade" 0.123
And I unplug USB drive "__internal" 0.128
After features/support/hooks.rb:339 1.885
After features/support/hooks.rb:108 0.000
Tags: @product
1:8.300
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.077
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.713
Then all tps features from the old Tails version are active 1.132
And Tails is running from USB drive "to_upgrade" 0.256
And the boot device has safe access rights 2.441
And the expected persistent files created with the old Tails version are present in the filesystem 1.046
And all persistent directories from the old Tails version have safe access rights 1.632
After features/support/hooks.rb:339 0.877
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:29.954
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.216
And no SquashFS delta is installed 0.055
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.274
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.190
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.351
When the network is plugged 0.034
And Tor is ready 12.384
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.897
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.126
Given I shutdown Tails and wait for the computer to power off 5.249
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.869
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.238
And the file system changes introduced in version 6.2~testoverlayfs are present 0.199
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.126
# 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.184
When the network is plugged 0.034
And Tor is ready 10.209
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.970
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.727
Given I shutdown Tails and wait for the computer to power off 3.940
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.959
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.076
And the file system changes introduced in version 6.3~testoverlayfs are present 0.369
And only the 6.3~testoverlayfs SquashFS delta is installed 0.045
# 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.131
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.154
When the network is plugged 0.032
And Tor is ready 9.968
Then the Upgrader considers the system as up-to-date 0.079
# 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.456
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.279
After features/support/hooks.rb:339 0.798
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
20.330
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.175
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.273
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
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.031
And Tor is ready 10.258
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.496
After features/support/hooks.rb:339 0.864
After features/support/hooks.rb:108 0.000