Project Number Date
test_Tails_ISO_stable 6535 27 Jul 2026, 18:14

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 12:44.086 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:19.375
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.061
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 15.165
When I start Tails from USB drive "old" with network unplugged 59.660
Then the boot device has safe access rights 2.710
And Tails is running from USB drive "old" 0.270
And there is no persistence partition on USB drive "old" 0.051
And process "udev-watchdog" is running 0.046
And udev-watchdog is monitoring the correct device 0.209
And I unplug USB drive "old" 0.173
After features/support/hooks.rb:339 1.608
After features/support/hooks.rb:108 0.006
Tags: @product
1:35.697
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.065
And I start Tails from USB drive "old" with network unplugged and I login 58.722
Then Tails is running from USB drive "old" 0.291
And I create a persistent partition 26.875
And I take note of which tps features are available 4.609
Then a Tails persistence partition exists on USB drive "old" 0.582
And I shutdown Tails and wait for the computer to power off 4.550
After features/support/hooks.rb:339 0.206
After features/support/hooks.rb:108 0.008
Tags: @product
1:47.714
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.068
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:12.495
Then Tails is running from USB drive "old" 0.267
And all tps features are active 6.779
When I write some files expected to persist 1.402
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.244
And all persistence configuration files have safe access rights 0.373
And all persistent directories from the old Tails version have safe access rights 2.420
And I take note of which tps features are available 5.558
And I shutdown Tails and wait for the computer to power off 4.183
# 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" 13.919
After features/support/hooks.rb:339 0.240
After features/support/hooks.rb:108 0.008
Tags: @product
2:14.985
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.005
And I log in to a new session 13.510
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.161
And I plug USB drive "to_upgrade" 2.347
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.745
Then the running Tails is installed on USB drive "to_upgrade" 15.908
And I unplug USB drive "to_upgrade" 0.147
And I unplug USB drive "__internal" 0.158
After features/support/hooks.rb:339 2.177
After features/support/hooks.rb:108 0.000
Tags: @product
1:19.281
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.188
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:11.577
Then all tps features from the old Tails version are active 1.090
And Tails is running from USB drive "to_upgrade" 0.263
And the boot device has safe access rights 2.701
And the expected persistent files created with the old Tails version are present in the filesystem 1.271
And all persistent directories from the old Tails version have safe access rights 2.187
After features/support/hooks.rb:339 0.508
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
4:5.635
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.721
And no SquashFS delta is installed 0.104
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.312
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.250
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.432
When the network is plugged 0.015
And Tor is ready 14.399
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.770
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.896
Given I shutdown Tails and wait for the computer to power off 7.055
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.390
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 5.414
And the file system changes introduced in version 6.2~testoverlayfs are present 0.304
And only the 6.2~testoverlayfs SquashFS delta is installed 0.040
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.144
# 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.202
When the network is plugged 0.018
And Tor is ready 12.360
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.337
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.597
Given I shutdown Tails and wait for the computer to power off 4.487
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.563
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.180
And the file system changes introduced in version 6.3~testoverlayfs are present 0.387
And only the 6.3~testoverlayfs SquashFS delta is installed 0.061
# 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.148
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.219
When the network is plugged 0.016
And Tor is ready 12.486
Then the Upgrader considers the system as up-to-date 10.836
# 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.961
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.428
After features/support/hooks.rb:339 0.906
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
21.396
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.684
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.274
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the signing key used by the Upgrader is outdated 0.054
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 9.701
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.622
After features/support/hooks.rb:339 0.838
After features/support/hooks.rb:108 0.000