Project Number Date
test_Tails_ISO_21318-tor-browser-16.0 26 27 Jun 2026, 08:06

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:36.960 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:3.162
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.049
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.168
When I start Tails from USB drive "old" with network unplugged 45.769
Then the boot device has safe access rights 2.436
And Tails is running from USB drive "old" 0.223
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.037
And udev-watchdog is monitoring the correct device 0.249
And I unplug USB drive "old" 0.158
After features/support/hooks.rb:339 3.420
After features/support/hooks.rb:108 0.008
Tags: @product
1:29.580
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login 52.474
Then Tails is running from USB drive "old" 0.229
And I create a persistent partition 24.531
And I take note of which tps features are available 3.788
Then a Tails persistence partition exists on USB drive "old" 0.547
And I shutdown Tails and wait for the computer to power off 7.956
After features/support/hooks.rb:339 0.281
After features/support/hooks.rb:108 0.006
Tags: @product
1:35.308
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.058
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.422
Then Tails is running from USB drive "old" 0.219
And all tps features are active 4.561
When I write some files expected to persist 1.151
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.151
And all persistence configuration files have safe access rights 0.311
And all persistent directories from the old Tails version have safe access rights 2.031
And I take note of which tps features are available 3.700
And I shutdown Tails and wait for the computer to power off 7.857
# 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.841
After features/support/hooks.rb:339 0.524
After features/support/hooks.rb:108 0.006
Tags: @product
2:10.998
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 8.076
And I log in to a new session 12.759
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.841
And I plug USB drive "to_upgrade" 2.215
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.377
Then the running Tails is installed on USB drive "to_upgrade" 15.475
And I unplug USB drive "to_upgrade" 0.125
And I unplug USB drive "__internal" 0.127
After features/support/hooks.rb:339 2.090
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.847
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.052
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.228
Then all tps features from the old Tails version are active 1.042
And Tails is running from USB drive "to_upgrade" 0.295
And the boot device has safe access rights 2.419
And the expected persistent files created with the old Tails version are present in the filesystem 1.140
And all persistent directories from the old Tails version have safe access rights 1.669
After features/support/hooks.rb:339 0.891
After features/support/hooks.rb:108 0.008
Tags: @product @automatic_upgrade
3:49.274
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.945
And no SquashFS delta is installed 0.073
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.251
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.217
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.308
When the network is plugged 0.040
And Tor is ready 13.335
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.634
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.408
Given I shutdown Tails and wait for the computer to power off 9.312
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.104
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.621
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.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.127
# 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.211
When the network is plugged 0.014
And Tor is ready 9.841
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.057
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.564
Given I shutdown Tails and wait for the computer to power off 7.923
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.566
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 4.866
And the file system changes introduced in version 6.3~testoverlayfs are present 0.365
And only the 6.3~testoverlayfs SquashFS delta is installed 0.045
# 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.155
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.204
When the network is plugged 0.016
And Tor is ready 11.008
Then the Upgrader considers the system as up-to-date 10.532
# 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.831
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.335
After features/support/hooks.rb:339 0.669
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
18.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 with a persistent partition enabled and logged in 7.631
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.242
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the signing key used by the Upgrader is outdated 0.055
But a current signing key is available on our website 0.000
When the network is plugged 0.030
And Tor is ready 9.099
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.680
After features/support/hooks.rb:339 0.944
After features/support/hooks.rb:108 0.000