Project Number Date
test_Tails_ISO_devel 4535 08 Aug 2026, 11:22

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:9.214 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:8.087
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.081
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.477
When I start Tails from USB drive "old" with network unplugged 50.663
Then the boot device has safe access rights 2.226
And Tails is running from USB drive "old" 0.243
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.045
And udev-watchdog is monitoring the correct device 0.146
And I unplug USB drive "old" 0.113
After features/support/hooks.rb:339 3.450
After features/support/hooks.rb:108 0.014
Tags: @product
1:30.889
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.114
And I start Tails from USB drive "old" with network unplugged and I login 52.620
Then Tails is running from USB drive "old" 0.172
And I create a persistent partition 25.704
And I take note of which tps features are available 7.527
Then a Tails persistence partition exists on USB drive "old" 0.624
And I shutdown Tails and wait for the computer to power off 4.124
After features/support/hooks.rb:339 0.499
After features/support/hooks.rb:108 0.006
Tags: @product
1:45.369
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.090
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:8.121
Then Tails is running from USB drive "old" 0.294
And all tps features are active 8.098
When I write some files expected to persist 1.130
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.135
And all persistence configuration files have safe access rights 0.240
And all persistent directories from the old Tails version have safe access rights 1.565
And I take note of which tps features are available 9.312
And I shutdown Tails and wait for the computer to power off 4.501
# 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.878
After features/support/hooks.rb:339 0.604
After features/support/hooks.rb:108 0.025
Tags: @product
2:18.639
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.230
And I log in to a new session 14.299
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.113
And I plug USB drive "to_upgrade" 2.253
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.436
Then the running Tails is installed on USB drive "to_upgrade" 20.069
And I unplug USB drive "to_upgrade" 0.117
And I unplug USB drive "__internal" 0.119
After features/support/hooks.rb:339 3.585
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.072
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.107
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.824
Then all tps features from the old Tails version are active 1.325
And Tails is running from USB drive "to_upgrade" 0.251
And the boot device has safe access rights 2.774
And the expected persistent files created with the old Tails version are present in the filesystem 1.161
And all persistent directories from the old Tails version have safe access rights 1.627
After features/support/hooks.rb:339 0.665
After features/support/hooks.rb:108 0.023
Tags: @product @automatic_upgrade
3:54.108
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.687
And no SquashFS delta is installed 0.095
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.287
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.228
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.397
When the network is plugged 0.033
And Tor is ready 13.199
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.020
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.338
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.706
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 8.531
And the file system changes introduced in version 6.2~testoverlayfs are present 0.229
And only the 6.2~testoverlayfs SquashFS delta is installed 0.043
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.142
# 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.195
When the network is plugged 0.033
And Tor is ready 10.423
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.632
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.132
Given I shutdown Tails and wait for the computer to power off 3.894
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.016
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 8.096
And the file system changes introduced in version 6.3~testoverlayfs are present 0.413
And only the 6.3~testoverlayfs SquashFS delta is installed 0.057
# 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.130
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.166
When the network is plugged 0.025
And Tor is ready 10.655
Then the Upgrader considers the system as up-to-date 10.531
# 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.528
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.518
After features/support/hooks.rb:339 0.851
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
20.046
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.050
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.210
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 0.036
But a current signing key is available on our website 0.000
When the network is plugged 0.042
And Tor is ready 9.153
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.505
After features/support/hooks.rb:339 0.646
After features/support/hooks.rb:108 0.000