Project Number Date
test_Tails_ISO_devel 4606 09 Sep 2026, 19:30

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:20.465 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
58.017
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.108
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 14.079
When I start Tails from USB drive "old" with network unplugged 39.744
Then the boot device has safe access rights 2.388
And Tails is running from USB drive "old" 0.220
And there is no persistence partition on USB drive "old" 0.053
And process "udev-watchdog" is running 0.048
And udev-watchdog is monitoring the correct device 0.222
And I unplug USB drive "old" 0.112
After features/support/hooks.rb:339 3.545
After features/support/hooks.rb:108 0.013
Tags: @product
1:24.851
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.114
And I start Tails from USB drive "old" with network unplugged and I login 50.836
Then Tails is running from USB drive "old" 0.204
And I create a persistent partition 24.245
And I take note of which tps features are available 6.211
Then a Tails persistence partition exists on USB drive "old" 0.649
And I shutdown Tails and wait for the computer to power off 2.589
After features/support/hooks.rb:339 0.525
After features/support/hooks.rb:108 0.005
Tags: @product
1:34.834
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.117
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.959
Then Tails is running from USB drive "old" 0.181
And all tps features are active 7.240
When I write some files expected to persist 1.426
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.204
And all persistence configuration files have safe access rights 0.375
And all persistent directories from the old Tails version have safe access rights 1.786
And I take note of which tps features are available 6.073
And I shutdown Tails and wait for the computer to power off 2.520
# 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.947
After features/support/hooks.rb:339 0.510
After features/support/hooks.rb:108 0.005
Tags: @product
2:13.602
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 8.483
And I log in to a new session 12.163
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.941
And I plug USB drive "to_upgrade" 2.249
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.560
Then the running Tails is installed on USB drive "to_upgrade" 17.981
And I unplug USB drive "to_upgrade" 0.106
And I unplug USB drive "__internal" 0.115
After features/support/hooks.rb:339 0.789
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.371
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.128
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.798
Then all tps features from the old Tails version are active 1.094
And Tails is running from USB drive "to_upgrade" 0.235
And the boot device has safe access rights 2.415
And the expected persistent files created with the old Tails version are present in the filesystem 0.991
And all persistent directories from the old Tails version have safe access rights 1.707
After features/support/hooks.rb:339 0.799
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:39.508
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 8.485
And no SquashFS delta is installed 0.094
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.208
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.259
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.402
When the network is plugged 0.029
And Tor is ready 13.434
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.348
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.849
Given I shutdown Tails and wait for the computer to power off 5.645
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.652
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.460
And the file system changes introduced in version 6.2~testoverlayfs are present 0.189
And only the 6.2~testoverlayfs SquashFS delta is installed 0.056
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.118
# 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.183
When the network is plugged 0.034
And Tor is ready 10.574
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.051
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.851
Given I shutdown Tails and wait for the computer to power off 2.586
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.921
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.719
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.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.119
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.155
When the network is plugged 0.026
And Tor is ready 10.484
Then the Upgrader considers the system as up-to-date 0.090
# 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.582
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.375
After features/support/hooks.rb:339 0.834
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
19.280
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.283
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.240
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
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.031
And Tor is ready 9.632
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.976
After features/support/hooks.rb:339 0.870
After features/support/hooks.rb:108 0.000