Project Number Date
test_Tails_ISO_19074-user-js-symlink 2 12 Aug 2026, 15:03

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:3.120 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.154
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.076
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.064
When I start Tails from USB drive "old" with network unplugged 44.645
Then the boot device has safe access rights 1.825
And Tails is running from USB drive "old" 0.156
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.049
And udev-watchdog is monitoring the correct device 0.145
And I unplug USB drive "old" 0.111
After features/support/hooks.rb:339 3.405
After features/support/hooks.rb:108 0.063
Tags: @product
1:17.281
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.071
And I start Tails from USB drive "old" with network unplugged and I login 45.600
Then Tails is running from USB drive "old" 0.196
And I create a persistent partition 22.265
And I take note of which tps features are available 6.185
Then a Tails persistence partition exists on USB drive "old" 0.420
And I shutdown Tails and wait for the computer to power off 2.541
After features/support/hooks.rb:339 0.559
After features/support/hooks.rb:108 0.005
Tags: @product
1:27.365
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.084
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.387
Then Tails is running from USB drive "old" 0.164
And all tps features are active 6.512
When I write some files expected to persist 0.885
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.103
And all persistence configuration files have safe access rights 0.210
And all persistent directories from the old Tails version have safe access rights 1.635
And I take note of which tps features are available 5.927
And I shutdown Tails and wait for the computer to power off 2.529
# 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" 10.925
After features/support/hooks.rb:339 0.437
After features/support/hooks.rb:108 0.005
Tags: @product
2:11.206
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.262
And I log in to a new session 11.925
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.631
And I plug USB drive "to_upgrade" 2.187
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.300
Then the running Tails is installed on USB drive "to_upgrade" 17.644
And I unplug USB drive "to_upgrade" 0.134
And I unplug USB drive "__internal" 0.119
After features/support/hooks.rb:339 0.589
After features/support/hooks.rb:108 0.000
Tags: @product
1:5.736
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.074
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.272
Then all tps features from the old Tails version are active 0.970
And Tails is running from USB drive "to_upgrade" 0.174
And the boot device has safe access rights 1.952
And the expected persistent files created with the old Tails version are present in the filesystem 0.843
And all persistent directories from the old Tails version have safe access rights 1.448
After features/support/hooks.rb:339 0.905
After features/support/hooks.rb:108 0.038
3:29.471
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 8.110
And no SquashFS delta is installed 0.093
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.187
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.194
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.334
When the network is plugged 0.048
And Tor is ready 12.087
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.477
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.274
Given I shutdown Tails and wait for the computer to power off 5.321
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.386
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.234
And the file system changes introduced in version 6.2~testoverlayfs are present 0.161
And only the 6.2~testoverlayfs SquashFS delta is installed 0.039
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.096
# 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.187
When the network is plugged 0.026
And Tor is ready 10.115
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.832
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.375
Given I shutdown Tails and wait for the computer to power off 2.559
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.626
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.253
And the file system changes introduced in version 6.3~testoverlayfs are present 0.372
And only the 6.3~testoverlayfs SquashFS delta is installed 0.049
# 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.198
When the network is plugged 0.026
And Tor is ready 9.875
Then the Upgrader considers the system as up-to-date 10.408
# 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.019
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.344
After features/support/hooks.rb:339 0.871
After features/support/hooks.rb:108 0.009
30.904
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 20.707
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.027
And the signing key used by the Upgrader is outdated 0.038
But a current signing key is available on our website 0.000
When the network is plugged 0.038
And Tor is ready 7.876
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.011
After features/support/hooks.rb:339 0.799
After features/support/hooks.rb:108 0.000