Project Number Date
test_Tails_ISO_21472-circumvention-settings-2 14 09 Apr 2026, 02:34

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 13:21.922 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:33.653
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.107
And I create a 7200 MiB disk named "old" 0.013
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 14.256
When I start Tails from USB drive "old" with network unplugged 1:14.838
Then the boot device has safe access rights 2.738
And Tails is running from USB drive "old" 0.259
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.045
And udev-watchdog is monitoring the correct device 0.189
And I unplug USB drive "old" 0.135
After features/support/hooks.rb:331 1.241
After features/support/hooks.rb:100 0.011
Tags: @product
1:32.115
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.150
And I start Tails from USB drive "old" with network unplugged and I login 56.864
Then Tails is running from USB drive "old" 0.250
And I create a persistent partition 25.108
And I take note of which tps features are available 0.723
Then a Tails persistence partition exists on USB drive "old" 0.593
And I shutdown Tails and wait for the computer to power off 8.424
After features/support/hooks.rb:331 0.311
After features/support/hooks.rb:100 0.006
Tags: @product
1:24.308
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.055
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.733
Then Tails is running from USB drive "old" 0.246
And all tps features are active 1.099
When I write some files expected to persist 1.400
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.179
And all persistence configuration files have safe access rights 0.464
And all persistent directories from the old Tails version have safe access rights 1.955
And I take note of which tps features are available 0.153
And I shutdown Tails and wait for the computer to power off 4.302
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.717
After features/support/hooks.rb:331 0.519
After features/support/hooks.rb:100 0.008
Tags: @product
2:17.819
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 7.983
And I log in to a new session 17.191
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.956
And I plug USB drive "to_upgrade" 2.232
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.304
Then the running Tails is installed on USB drive "to_upgrade" 16.881
And I unplug USB drive "to_upgrade" 0.138
And I unplug USB drive "__internal" 0.131
After features/support/hooks.rb:331 3.940
After features/support/hooks.rb:100 0.000
Tags: @product
1:14.977
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.055
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.723
Then all tps features from the old Tails version are active 1.082
And Tails is running from USB drive "to_upgrade" 0.286
And the boot device has safe access rights 2.780
And the expected persistent files created with the old Tails version are present in the filesystem 1.152
And all persistent directories from the old Tails version have safe access rights 1.897
After features/support/hooks.rb:331 0.782
After features/support/hooks.rb:100 0.025
4:51.116
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 with a persistent partition enabled and logged in 9.041
And no SquashFS delta is installed 0.158
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.360
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.242
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.427
When the network is plugged 0.021
And Tor is ready 25.157
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.477
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.581
Given I shutdown Tails and wait for the computer to power off 19.763
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.235
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.139
And the file system changes introduced in version 6.2~testoverlayfs are present 0.260
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.131
# 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.225
When the network is plugged 0.016
And Tor is ready 21.057
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.429
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.625
Given I shutdown Tails and wait for the computer to power off 17.195
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.272
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 1.370
And the file system changes introduced in version 6.3~testoverlayfs are present 0.415
And only the 6.3~testoverlayfs SquashFS delta is installed 0.054
# 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.148
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.198
When the network is plugged 0.015
And Tor is ready 22.580
Then the Upgrader considers the system as up-to-date 0.160
# 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.817
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.436
After features/support/hooks.rb:331 0.908
After features/support/hooks.rb:100 0.010
27.932
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 with a persistent partition enabled and logged in 7.499
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.264
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the signing key used by the Upgrader is outdated 0.047
But a current signing key is available on our website 0.000
When the network is plugged 0.021
And Tor is ready 19.711
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.349
After features/support/hooks.rb:331 0.989
After features/support/hooks.rb:100 0.000