Project Number Date
test_Tails_ISO_21318-tor-browser-16.0 3 04 Jun 2026, 20:41

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:44.099 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:20.155
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.085
And I create a 7200 MiB disk named "old" 0.014
And I plug USB drive "old" 1.027
And I write an old version of the Tails USB image to disk "old" 13.790
When I start Tails from USB drive "old" with network unplugged 1:1.968
Then the boot device has safe access rights 2.584
And Tails is running from USB drive "old" 0.257
And there is no persistence partition on USB drive "old" 0.036
And process "udev-watchdog" is running 0.059
And udev-watchdog is monitoring the correct device 0.199
And I unplug USB drive "old" 0.132
After features/support/hooks.rb:335 3.452
After features/support/hooks.rb:104 0.006
Tags: @product
1:27.974
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login 53.105
Then Tails is running from USB drive "old" 0.236
And I create a persistent partition 25.222
And I take note of which tps features are available 0.468
Then a Tails persistence partition exists on USB drive "old" 0.568
And I shutdown Tails and wait for the computer to power off 8.322
After features/support/hooks.rb:335 0.439
After features/support/hooks.rb:104 0.008
Tags: @product
1:30.157
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.072
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.111
Then Tails is running from USB drive "old" 0.215
And all tps features are active 1.158
When I write some files expected to persist 1.283
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.206
And all persistence configuration files have safe access rights 0.284
And all persistent directories from the old Tails version have safe access rights 2.116
And I take note of which tps features are available 0.211
And I shutdown Tails and wait for the computer to power off 8.386
# 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.109
After features/support/hooks.rb:335 0.132
After features/support/hooks.rb:104 0.007
Tags: @product
2:13.232
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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.386
And I log in to a new session 13.690
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.857
And I plug USB drive "to_upgrade" 2.226
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.120
Then the running Tails is installed on USB drive "to_upgrade" 15.667
And I unplug USB drive "to_upgrade" 0.139
And I unplug USB drive "__internal" 0.144
After features/support/hooks.rb:335 2.302
After features/support/hooks.rb:104 0.000
Tags: @product
1:11.364
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.051
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.740
Then all tps features from the old Tails version are active 1.338
And Tails is running from USB drive "to_upgrade" 0.245
And the boot device has safe access rights 2.664
And the expected persistent files created with the old Tails version are present in the filesystem 1.270
And all persistent directories from the old Tails version have safe access rights 2.053
After features/support/hooks.rb:335 0.923
After features/support/hooks.rb:104 0.008
3:41.138
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.301
And no SquashFS delta is installed 0.077
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.272
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.271
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.373
When the network is plugged 0.023
And Tor is ready 13.384
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.372
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.345
Given I shutdown Tails and wait for the computer to power off 7.077
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.642
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.110
And the file system changes introduced in version 6.2~testoverlayfs are present 0.237
And only the 6.2~testoverlayfs SquashFS delta is installed 0.051
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.144
# 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.014
And Tor is ready 9.887
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.769
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.042
Given I shutdown Tails and wait for the computer to power off 8.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.592
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 1.282
And the file system changes introduced in version 6.3~testoverlayfs are present 0.459
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.166
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.226
When the network is plugged 0.015
And Tor is ready 11.145
Then the Upgrader considers the system as up-to-date 10.522
# 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.519
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.443
After features/support/hooks.rb:335 0.770
After features/support/hooks.rb:104 0.012
20.076
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.448
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.261
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.077
And the signing key used by the Upgrader is outdated 0.071
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 10.074
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.128
After features/support/hooks.rb:335 0.654
After features/support/hooks.rb:104 0.000