Project Number Date
test_Tails_ISO_21318-tor-browser-16.0 52 24 Jul 2026, 08:10

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:41.548 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:15.199
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.097
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 13.361
When I start Tails from USB drive "old" with network unplugged 57.224
Then the boot device has safe access rights 2.728
And Tails is running from USB drive "old" 0.274
And there is no persistence partition on USB drive "old" 0.049
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.256
And I unplug USB drive "old" 0.134
After features/support/hooks.rb:339 1.339
After features/support/hooks.rb:108 0.006
Tags: @product
1:26.244
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login 51.763
Then Tails is running from USB drive "old" 0.220
And I create a persistent partition 25.033
And I take note of which tps features are available 4.350
Then a Tails persistence partition exists on USB drive "old" 0.521
And I shutdown Tails and wait for the computer to power off 4.305
After features/support/hooks.rb:339 0.621
After features/support/hooks.rb:108 0.007
Tags: @product
1:31.863
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.318
Then Tails is running from USB drive "old" 0.234
And all tps features are active 4.759
When I write some files expected to persist 1.259
# 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.299
And all persistent directories from the old Tails version have safe access rights 2.122
And I take note of which tps features are available 4.059
And I shutdown Tails and wait for the computer to power off 4.328
# 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.280
After features/support/hooks.rb:339 0.506
After features/support/hooks.rb:108 0.006
Tags: @product
2:10.334
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 without a persistent partition and stopped at Tails Greeter's login screen 7.968
And I log in to a new session 12.226
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.904
And I plug USB drive "to_upgrade" 2.222
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.235
Then the running Tails is installed on USB drive "to_upgrade" 15.512
And I unplug USB drive "to_upgrade" 0.132
And I unplug USB drive "__internal" 0.131
After features/support/hooks.rb:339 2.038
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.390
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.045
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.200
Then all tps features from the old Tails version are active 0.947
And Tails is running from USB drive "to_upgrade" 0.313
And the boot device has safe access rights 2.614
And the expected persistent files created with the old Tails version are present in the filesystem 1.307
And all persistent directories from the old Tails version have safe access rights 1.960
After features/support/hooks.rb:339 0.847
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:48.162
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.919
And no SquashFS delta is installed 0.062
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.204
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.214
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.344
When the network is plugged 0.016
And Tor is ready 12.738
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.109
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.614
Given I shutdown Tails and wait for the computer to power off 6.965
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.890
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 4.599
And the file system changes introduced in version 6.2~testoverlayfs are present 0.193
And only the 6.2~testoverlayfs SquashFS delta is installed 0.047
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.120
# 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.191
When the network is plugged 0.014
And Tor is ready 10.977
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.629
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.815
Given I shutdown Tails and wait for the computer to power off 3.994
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.183
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.623
And the file system changes introduced in version 6.3~testoverlayfs are present 0.352
And only the 6.3~testoverlayfs SquashFS delta is installed 0.056
# 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.156
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.193
When the network is plugged 0.016
And Tor is ready 11.868
Then the Upgrader considers the system as up-to-date 10.517
# 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.122
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.331
After features/support/hooks.rb:339 0.707
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
20.354
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.281
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.206
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.013
And Tor is ready 9.739
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.022
After features/support/hooks.rb:339 0.867
After features/support/hooks.rb:108 0.000