Project Number Date
test_Tails_ISO_devel 4297 27 Mar 2026, 11:28

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:33.421 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.111
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.053
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.719
When I start Tails from USB drive "old" with network unplugged 50.114
Then the boot device has safe access rights 2.489
And Tails is running from USB drive "old" 0.255
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.048
And udev-watchdog is monitoring the correct device 0.219
And I unplug USB drive "old" 0.129
After features/support/hooks.rb:331 3.449
After features/support/hooks.rb:100 0.006
Tags: @product
1:25.800
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.046
And I start Tails from USB drive "old" with network unplugged and I login 51.608
Then Tails is running from USB drive "old" 0.234
And I create a persistent partition 24.381
And I take note of which tps features are available 0.642
Then a Tails persistence partition exists on USB drive "old" 0.534
And I shutdown Tails and wait for the computer to power off 8.353
After features/support/hooks.rb:331 0.532
After features/support/hooks.rb:100 0.007
Tags: @product
1:24.419
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.050
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.244
Then Tails is running from USB drive "old" 0.239
And all tps features are active 1.128
When I write some files expected to persist 1.315
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.139
And all persistence configuration files have safe access rights 0.402
And all persistent directories from the old Tails version have safe access rights 1.719
And I take note of which tps features are available 0.166
And I shutdown Tails and wait for the computer to power off 7.783
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.230
After features/support/hooks.rb:331 0.404
After features/support/hooks.rb:100 0.007
Tags: @product
2:22.530
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 7.409
And I log in to a new session 17.548
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.918
And I plug USB drive "to_upgrade" 2.236
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.465
Then the running Tails is installed on USB drive "to_upgrade" 16.685
And I unplug USB drive "to_upgrade" 0.131
And I unplug USB drive "__internal" 0.135
After features/support/hooks.rb:331 2.169
After features/support/hooks.rb:100 0.000
Tags: @product
1:9.074
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.048
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.294
Then all tps features from the old Tails version are active 2.010
And Tails is running from USB drive "to_upgrade" 0.236
And the boot device has safe access rights 2.521
And the expected persistent files created with the old Tails version are present in the filesystem 1.118
And all persistent directories from the old Tails version have safe access rights 1.845
After features/support/hooks.rb:331 0.723
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
4:34.109
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.012
And no SquashFS delta is installed 0.061
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.186
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.035
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.183
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.327
When the network is plugged 0.090
And Tor is ready 24.204
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.387
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.710
Given I shutdown Tails and wait for the computer to power off 18.989
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.334
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.132
And the file system changes introduced in version 6.2~testoverlayfs are present 0.202
And only the 6.2~testoverlayfs SquashFS delta is installed 0.044
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.129
# 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.210
When the network is plugged 0.014
And Tor is ready 20.242
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.362
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.887
Given I shutdown Tails and wait for the computer to power off 17.050
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.690
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 0.993
And the file system changes introduced in version 6.3~testoverlayfs are present 0.324
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.140
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.225
When the network is plugged 0.016
And Tor is ready 20.938
Then the Upgrader considers the system as up-to-date 0.116
# 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.369
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.444
After features/support/hooks.rb:331 0.949
After features/support/hooks.rb:100 0.036
Tags: @product @automatic_upgrade
29.374
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.732
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.367
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the signing key used by the Upgrader is outdated 0.057
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 20.799
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.352
After features/support/hooks.rb:331 0.823
After features/support/hooks.rb:100 0.000