Project Number Date
test_Tails_ISO_21318-tor-browser-16.0 17 17 Jun 2026, 20:15

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:26.057 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:1.887
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given a computer 0.196
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.033
And I write an old version of the Tails USB image to disk "old" 12.798
When I start Tails from USB drive "old" with network unplugged 44.908
Then the boot device has safe access rights 2.293
And Tails is running from USB drive "old" 0.203
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.184
And I unplug USB drive "old" 0.143
After features/support/hooks.rb:339 1.324
After features/support/hooks.rb:108 0.019
Tags: @product
1:25.426
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.033
Given a computer 0.109
And I start Tails from USB drive "old" with network unplugged and I login 53.479
Then Tails is running from USB drive "old" 0.212
And I create a persistent partition 24.130
And I take note of which tps features are available 4.216
Then a Tails persistence partition exists on USB drive "old" 0.462
And I shutdown Tails and wait for the computer to power off 2.815
After features/support/hooks.rb:339 0.436
After features/support/hooks.rb:108 0.018
Tags: @product
1:32.003
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given a computer 0.105
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.501
Then Tails is running from USB drive "old" 0.288
And all tps features are active 4.904
When I write some files expected to persist 1.363
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.223
And all persistence configuration files have safe access rights 0.332
And all persistent directories from the old Tails version have safe access rights 1.930
And I take note of which tps features are available 3.760
And I shutdown Tails and wait for the computer to power off 2.751
# 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.285
After features/support/hooks.rb:108 0.019
Tags: @product
2:9.157
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.978
And I log in to a new session 11.422
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.783
And I plug USB drive "to_upgrade" 2.229
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.932
Then the running Tails is installed on USB drive "to_upgrade" 15.544
And I unplug USB drive "to_upgrade" 0.139
And I unplug USB drive "__internal" 0.127
After features/support/hooks.rb:339 6.713
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.138
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.057
Given a computer 0.116
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.026
Then all tps features from the old Tails version are active 1.088
And Tails is running from USB drive "to_upgrade" 0.267
And the boot device has safe access rights 2.470
And the expected persistent files created with the old Tails version are present in the filesystem 1.184
And all persistent directories from the old Tails version have safe access rights 1.984
After features/support/hooks.rb:339 0.548
After features/support/hooks.rb:108 0.021
Tags: @product @automatic_upgrade
3:46.430
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.014
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.178
And no SquashFS delta is installed 0.123
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.270
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.261
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.410
When the network is plugged 0.022
And Tor is ready 12.515
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.881
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.118
Given I shutdown Tails and wait for the computer to power off 9.655
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.161
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 4.909
And the file system changes introduced in version 6.2~testoverlayfs are present 0.198
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.128
# 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.286
When the network is plugged 0.021
And Tor is ready 9.805
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.353
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.426
Given I shutdown Tails and wait for the computer to power off 6.913
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.870
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.597
And the file system changes introduced in version 6.3~testoverlayfs are present 0.386
And only the 6.3~testoverlayfs SquashFS delta is installed 0.037
# 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.138
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.178
When the network is plugged 0.014
And Tor is ready 10.344
Then the Upgrader considers the system as up-to-date 10.505
# 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.188
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.401
After features/support/hooks.rb:339 0.898
After features/support/hooks.rb:108 0.032
Tags: @product @automatic_upgrade
20.013
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.626
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.265
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
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.019
And Tor is ready 9.288
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.701
After features/support/hooks.rb:339 0.746
After features/support/hooks.rb:108 0.000