Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 11 06 May 2026, 20:22

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:54.552 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:8.898
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.050
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.160
When I start Tails from USB drive "old" with network unplugged 51.673
Then the boot device has safe access rights 2.304
And Tails is running from USB drive "old" 0.237
And there is no persistence partition on USB drive "old" 0.037
And process "udev-watchdog" is running 0.060
And udev-watchdog is monitoring the correct device 0.193
And I unplug USB drive "old" 0.155
After features/support/hooks.rb:331 3.679
After features/support/hooks.rb:100 0.038
Tags: @product
1:19.606
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.062
And I start Tails from USB drive "old" with network unplugged and I login 50.409
Then Tails is running from USB drive "old" 0.285
And I create a persistent partition 23.499
And I take note of which tps features are available 0.721
Then a Tails persistence partition exists on USB drive "old" 0.480
And I shutdown Tails and wait for the computer to power off 4.147
After features/support/hooks.rb:331 0.266
After features/support/hooks.rb:100 0.006
Tags: @product
1:22.078
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.373
Then Tails is running from USB drive "old" 0.285
And all tps features are active 1.111
When I write some files expected to persist 1.224
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.153
And all persistence configuration files have safe access rights 0.400
And all persistent directories from the old Tails version have safe access rights 1.715
And I take note of which tps features are available 0.145
And I shutdown Tails and wait for the computer to power off 7.934
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.680
After features/support/hooks.rb:331 0.279
After features/support/hooks.rb:100 0.007
Tags: @product
2:10.042
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 7.324
And I log in to a new session 12.511
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.702
And I plug USB drive "to_upgrade" 2.220
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.969
Then the running Tails is installed on USB drive "to_upgrade" 15.034
And I unplug USB drive "to_upgrade" 0.144
And I unplug USB drive "__internal" 0.134
After features/support/hooks.rb:331 2.223
After features/support/hooks.rb:100 0.000
Tags: @product
1:6.264
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.057
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.555
Then all tps features from the old Tails version are active 0.886
And Tails is running from USB drive "to_upgrade" 0.292
And the boot device has safe access rights 2.571
And the expected persistent files created with the old Tails version are present in the filesystem 1.064
And all persistent directories from the old Tails version have safe access rights 1.836
After features/support/hooks.rb:331 0.948
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
4:22.287
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.707
And no SquashFS delta is installed 0.057
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.267
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.262
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.363
When the network is plugged 0.014
And Tor is ready 21.239
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.390
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.591
Given I shutdown Tails and wait for the computer to power off 19.969
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.299
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.114
And the file system changes introduced in version 6.2~testoverlayfs are present 0.200
And only the 6.2~testoverlayfs SquashFS delta is installed 0.043
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.134
# 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.181
When the network is plugged 0.014
And Tor is ready 19.953
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.374
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.787
Given I shutdown Tails and wait for the computer to power off 13.096
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.438
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.063
And the file system changes introduced in version 6.3~testoverlayfs are present 0.404
And only the 6.3~testoverlayfs SquashFS delta is installed 0.058
# 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.129
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.224
When the network is plugged 0.019
And Tor is ready 20.266
Then the Upgrader considers the system as up-to-date 0.098
# 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.043
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.403
After features/support/hooks.rb:331 1.045
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
25.375
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.139
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.199
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the signing key used by the Upgrader is outdated 0.062
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 17.525
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.387
After features/support/hooks.rb:331 0.823
After features/support/hooks.rb:100 0.000