Project Number Date
test_Tails_ISO_devel 4202 31 Jan 2026, 11:48

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:43.468 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:20.097
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.049
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 13.853
When I start Tails from USB drive "old" with network unplugged 1:1.377
Then the boot device has safe access rights 3.100
And Tails is running from USB drive "old" 0.228
And there is no persistence partition on USB drive "old" 0.081
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.195
And I unplug USB drive "old" 0.129
After features/support/hooks.rb:331 3.594
After features/support/hooks.rb:100 0.048
Tags: @product
1:25.621
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login 54.962
Then Tails is running from USB drive "old" 0.280
And I create a persistent partition 24.763
And I take note of which tps features are available 0.673
Then a Tails persistence partition exists on USB drive "old" 0.602
And I shutdown Tails and wait for the computer to power off 4.287
After features/support/hooks.rb:331 0.254
After features/support/hooks.rb:100 0.006
Tags: @product
1:25.249
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.059
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.172
Then Tails is running from USB drive "old" 0.328
And all tps features are active 1.241
When I write some files expected to persist 1.283
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.225
And all persistence configuration files have safe access rights 0.299
And all persistent directories from the old Tails version have safe access rights 1.987
And I take note of which tps features are available 0.188
And I shutdown Tails and wait for the computer to power off 4.034
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.428
After features/support/hooks.rb:331 0.140
After features/support/hooks.rb:100 0.007
Tags: @product
2:13.578
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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.819
And I log in to a new session 11.540
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.020
And I plug USB drive "to_upgrade" 2.360
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.342
Then the running Tails is installed on USB drive "to_upgrade" 16.230
And I unplug USB drive "to_upgrade" 0.125
And I unplug USB drive "__internal" 0.139
After features/support/hooks.rb:331 2.412
After features/support/hooks.rb:100 0.000
Tags: @product
1:9.571
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.049
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.085
Then all tps features from the old Tails version are active 1.047
And Tails is running from USB drive "to_upgrade" 0.255
And the boot device has safe access rights 2.811
And the expected persistent files created with the old Tails version are present in the filesystem 1.238
And all persistent directories from the old Tails version have safe access rights 2.083
After features/support/hooks.rb:331 0.733
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
3:49.130
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 8.015
And no SquashFS delta is installed 0.053
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.259
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.131
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.198
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.676
When the network is plugged 0.014
And Tor is ready 12.151
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.282
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.174
Given I shutdown Tails and wait for the computer to power off 9.901
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.666
Then Tails is running version 6.2~testoverlayfs 0.021
And all tps features are active 1.639
And the file system changes introduced in version 6.2~testoverlayfs are present 0.268
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.135
# 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.228
When the network is plugged 0.015
And Tor is ready 11.493
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.554
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.538
Given I shutdown Tails and wait for the computer to power off 7.090
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.050
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.014
And the file system changes introduced in version 6.3~testoverlayfs are present 0.342
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.151
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.217
When the network is plugged 0.019
And Tor is ready 11.435
Then the Upgrader considers the system as up-to-date 10.571
# 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.232
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.469
After features/support/hooks.rb:331 0.842
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
20.217
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.975
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.219
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.074
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 9.485
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.398
After features/support/hooks.rb:331 1.150
After features/support/hooks.rb:100 0.000