Project Number Date
test_Tails_ISO_21318-tor-browser-16.0 63 04 Aug 2026, 08:33

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:33.884 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:6.582
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.056
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 13.023
When I start Tails from USB drive "old" with network unplugged 49.282
Then the boot device has safe access rights 2.577
And Tails is running from USB drive "old" 0.219
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.059
And udev-watchdog is monitoring the correct device 0.172
And I unplug USB drive "old" 0.126
After features/support/hooks.rb:339 3.505
After features/support/hooks.rb:108 0.006
Tags: @product
1:23.451
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.043
And I start Tails from USB drive "old" with network unplugged and I login 51.876
Then Tails is running from USB drive "old" 0.209
And I create a persistent partition 23.059
And I take note of which tps features are available 3.792
Then a Tails persistence partition exists on USB drive "old" 0.504
And I shutdown Tails and wait for the computer to power off 3.966
After features/support/hooks.rb:339 0.402
After features/support/hooks.rb:108 0.007
Tags: @product
1:30.519
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.047
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.916
Then Tails is running from USB drive "old" 0.266
And all tps features are active 5.109
When I write some files expected to persist 1.307
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.220
And all persistence configuration files have safe access rights 0.317
And all persistent directories from the old Tails version have safe access rights 1.820
And I take note of which tps features are available 3.611
And I shutdown Tails and wait for the computer to power off 3.950
# 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.952
After features/support/hooks.rb:339 0.312
After features/support/hooks.rb:108 0.007
Tags: @product
2:8.788
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 7.930
And I log in to a new session 12.872
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.677
And I plug USB drive "to_upgrade" 2.237
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.361
Then the running Tails is installed on USB drive "to_upgrade" 13.428
And I unplug USB drive "to_upgrade" 0.150
And I unplug USB drive "__internal" 0.131
After features/support/hooks.rb:339 1.859
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.327
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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:2.726
Then all tps features from the old Tails version are active 0.934
And Tails is running from USB drive "to_upgrade" 0.237
And the boot device has safe access rights 2.335
And the expected persistent files created with the old Tails version are present in the filesystem 1.269
And all persistent directories from the old Tails version have safe access rights 1.772
After features/support/hooks.rb:339 0.920
After features/support/hooks.rb:108 0.008
Tags: @product @automatic_upgrade
3:55.603
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 with a persistent partition enabled and logged in 7.851
And no SquashFS delta is installed 0.063
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.041
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.199
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.373
When the network is plugged 0.018
And Tor is ready 16.825
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.769
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.394
Given I shutdown Tails and wait for the computer to power off 5.484
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.785
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.618
And the file system changes introduced in version 6.2~testoverlayfs are present 0.226
And only the 6.2~testoverlayfs SquashFS delta is installed 0.050
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.133
# 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.183
When the network is plugged 0.015
And Tor is ready 11.075
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.410
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.661
Given I shutdown Tails and wait for the computer to power off 4.015
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.132
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.873
And the file system changes introduced in version 6.3~testoverlayfs are present 0.293
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.250
When the network is plugged 0.015
And Tor is ready 20.268
Then the Upgrader considers the system as up-to-date 10.559
# 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.208
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.388
After features/support/hooks.rb:339 0.766
After features/support/hooks.rb:108 0.059
Tags: @product @automatic_upgrade
19.610
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 7.301
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.227
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
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.020
And Tor is ready 9.510
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.459
After features/support/hooks.rb:339 0.626
After features/support/hooks.rb:108 0.000