Project Number Date
test_Tails_ISO_stable-flatpak 31 29 Sep 2026, 19: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:39.009 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.763
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.097
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.031
And I write an old version of the Tails USB image to disk "old" 14.080
When I start Tails from USB drive "old" with network unplugged 1:0.592
Then the boot device has safe access rights 2.249
And Tails is running from USB drive "old" 0.229
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.041
And udev-watchdog is monitoring the correct device 0.249
And I unplug USB drive "old" 0.125
After features/support/hooks.rb:339 1.130
After features/support/hooks.rb:108 0.007
Tags: @product
1:32.980
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.007
Given a computer 0.116
And I start Tails from USB drive "old" with network unplugged and I login 51.520
Then Tails is running from USB drive "old" 0.299
And I create a persistent partition 26.987
And I take note of which tps features are available 9.416
Then a Tails persistence partition exists on USB drive "old" 0.615
And I shutdown Tails and wait for the computer to power off 4.024
After features/support/hooks.rb:339 0.391
After features/support/hooks.rb:108 0.010
Tags: @product
1:40.714
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.095
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.576
Then Tails is running from USB drive "old" 0.267
And all tps features are active 8.153
When I write some files expected to persist 1.774
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.164
And all persistence configuration files have safe access rights 0.295
And all persistent directories from the old Tails version have safe access rights 2.328
And I take note of which tps features are available 6.211
And I shutdown Tails and wait for the computer to power off 4.013
# 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.834
After features/support/hooks.rb:339 0.566
After features/support/hooks.rb:108 0.006
Tags: @product
2:14.920
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 8.459
And I log in to a new session 13.063
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.726
And I plug USB drive "to_upgrade" 2.201
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.396
Then the running Tails is installed on USB drive "to_upgrade" 18.837
And I unplug USB drive "to_upgrade" 0.120
And I unplug USB drive "__internal" 0.114
After features/support/hooks.rb:339 1.847
After features/support/hooks.rb:108 0.000
Tags: @product
1:15.178
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.087
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.884
Then all tps features from the old Tails version are active 1.195
And Tails is running from USB drive "to_upgrade" 0.239
And the boot device has safe access rights 2.467
And the expected persistent files created with the old Tails version are present in the filesystem 1.537
And all persistent directories from the old Tails version have safe access rights 2.765
After features/support/hooks.rb:339 0.607
After features/support/hooks.rb:108 0.015
Tags: @product @automatic_upgrade
4:14.687
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 23.041
And no SquashFS delta is installed 0.136
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.287
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.179
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.423
When the network is plugged 0.029
And Tor is ready 13.657
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.125
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.439
Given I shutdown Tails and wait for the computer to power off 5.348
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.569
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 9.322
And the file system changes introduced in version 6.2~testoverlayfs are present 0.243
And only the 6.2~testoverlayfs SquashFS delta is installed 0.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.129
# 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.179
When the network is plugged 0.031
And Tor is ready 11.405
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.219
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.210
Given I shutdown Tails and wait for the computer to power off 3.921
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.979
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 9.425
And the file system changes introduced in version 6.3~testoverlayfs are present 0.373
And only the 6.3~testoverlayfs SquashFS delta is installed 0.044
# 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.104
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.198
When the network is plugged 0.038
And Tor is ready 11.015
Then the Upgrader considers the system as up-to-date 10.486
# 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.722
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.282
After features/support/hooks.rb:339 0.783
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
21.766
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.804
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.207
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.033
And Tor is ready 9.623
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.006
After features/support/hooks.rb:339 1.250
After features/support/hooks.rb:108 0.000