Project Number Date
test_Tails_ISO_21318-tor-browser-16.0 67 10 Aug 2026, 08:04

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:28.467 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
59.694
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.083
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.024
And I write an old version of the Tails USB image to disk "old" 13.424
When I start Tails from USB drive "old" with network unplugged 42.591
Then the boot device has safe access rights 1.940
And Tails is running from USB drive "old" 0.211
And there is no persistence partition on USB drive "old" 0.039
And process "udev-watchdog" is running 0.048
And udev-watchdog is monitoring the correct device 0.184
And I unplug USB drive "old" 0.123
After features/support/hooks.rb:339 3.395
After features/support/hooks.rb:108 0.064
Tags: @product
1:19.148
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.098
And I start Tails from USB drive "old" with network unplugged and I login 46.770
Then Tails is running from USB drive "old" 0.158
And I create a persistent partition 22.799
And I take note of which tps features are available 6.195
Then a Tails persistence partition exists on USB drive "old" 0.507
And I shutdown Tails and wait for the computer to power off 2.618
After features/support/hooks.rb:339 0.187
After features/support/hooks.rb:108 0.005
Tags: @product
1:32.376
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.152
Then Tails is running from USB drive "old" 0.212
And all tps features are active 7.453
When I write some files expected to persist 1.076
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.114
And all persistence configuration files have safe access rights 0.225
And all persistent directories from the old Tails version have safe access rights 1.637
And I take note of which tps features are available 6.142
And I shutdown Tails and wait for the computer to power off 2.553
# 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.725
After features/support/hooks.rb:339 0.426
After features/support/hooks.rb:108 0.006
Tags: @product
2:12.054
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.021
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.065
And I log in to a new session 12.195
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.641
And I plug USB drive "to_upgrade" 2.230
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.497
Then the running Tails is installed on USB drive "to_upgrade" 17.191
And I unplug USB drive "to_upgrade" 0.125
And I unplug USB drive "__internal" 0.107
After features/support/hooks.rb:339 1.724
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.472
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.084
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.424
Then all tps features from the old Tails version are active 1.376
And Tails is running from USB drive "to_upgrade" 0.225
And the boot device has safe access rights 2.342
And the expected persistent files created with the old Tails version are present in the filesystem 1.138
And all persistent directories from the old Tails version have safe access rights 1.880
After features/support/hooks.rb:339 0.745
After features/support/hooks.rb:108 0.006
3:53.629
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 24.119
And no SquashFS delta is installed 0.083
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.300
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.284
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.385
When the network is plugged 0.035
And Tor is ready 13.403
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.392
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.427
Given I shutdown Tails and wait for the computer to power off 6.907
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.257
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 8.081
And the file system changes introduced in version 6.2~testoverlayfs are present 0.206
And only the 6.2~testoverlayfs SquashFS delta is installed 0.097
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.184
# 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.203
When the network is plugged 0.028
And Tor is ready 11.387
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.350
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.779
Given I shutdown Tails and wait for the computer to power off 3.949
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.270
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 7.775
And the file system changes introduced in version 6.3~testoverlayfs are present 0.343
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.100
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.197
When the network is plugged 0.026
And Tor is ready 10.624
Then the Upgrader considers the system as up-to-date 0.123
# 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.786
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.379
After features/support/hooks.rb:339 0.706
After features/support/hooks.rb:108 0.010
20.091
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.912
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.039
And the signing key used by the Upgrader is outdated 0.043
But a current signing key is available on our website 0.000
When the network is plugged 0.032
And Tor is ready 10.243
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.592
After features/support/hooks.rb:339 0.585
After features/support/hooks.rb:108 0.000