Project Number Date
test_Tails_ISO_devel 4306 31 Mar 2026, 07:44

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.030 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.352
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.069
And I create a 7200 MiB disk named "old" 0.012
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.873
When I start Tails from USB drive "old" with network unplugged 1:0.898
Then the boot device has safe access rights 2.802
And Tails is running from USB drive "old" 0.215
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.200
And I unplug USB drive "old" 0.165
After features/support/hooks.rb:331 1.332
After features/support/hooks.rb:100 0.006
Tags: @product
1:28.871
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.050
And I start Tails from USB drive "old" with network unplugged and I login 55.081
Then Tails is running from USB drive "old" 0.239
And I create a persistent partition 24.918
And I take note of which tps features are available 0.737
Then a Tails persistence partition exists on USB drive "old" 0.814
And I shutdown Tails and wait for the computer to power off 7.030
After features/support/hooks.rb:331 0.486
After features/support/hooks.rb:100 0.007
Tags: @product
1:22.079
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.093
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.761
Then Tails is running from USB drive "old" 0.278
And all tps features are active 1.087
When I write some files expected to persist 1.198
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.163
And all persistence configuration files have safe access rights 0.351
And all persistent directories from the old Tails version have safe access rights 1.759
And I take note of which tps features are available 0.205
And I shutdown Tails and wait for the computer to power off 2.640
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.539
After features/support/hooks.rb:331 0.289
After features/support/hooks.rb:100 0.007
Tags: @product
2:11.108
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.690
And I log in to a new session 12.510
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.743
And I plug USB drive "to_upgrade" 2.210
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.098
Then the running Tails is installed on USB drive "to_upgrade" 16.531
And I unplug USB drive "to_upgrade" 0.171
And I unplug USB drive "__internal" 0.151
After features/support/hooks.rb:331 2.004
After features/support/hooks.rb:100 0.000
Tags: @product
1:11.447
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:4.307
Then all tps features from the old Tails version are active 1.291
And Tails is running from USB drive "to_upgrade" 0.257
And the boot device has safe access rights 2.533
And the expected persistent files created with the old Tails version are present in the filesystem 1.046
And all persistent directories from the old Tails version have safe access rights 1.960
After features/support/hooks.rb:331 0.807
After features/support/hooks.rb:100 0.007
4:34.109
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.147
And no SquashFS delta is installed 0.078
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.262
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.286
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.525
When the network is plugged 0.017
And Tor is ready 21.018
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.473
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.281
Given I shutdown Tails and wait for the computer to power off 20.074
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.166
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 1.203
And the file system changes introduced in version 6.2~testoverlayfs are present 0.314
And only the 6.2~testoverlayfs SquashFS delta is installed 0.051
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.192
# 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.231
When the network is plugged 0.016
And Tor is ready 20.628
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.398
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.274
Given I shutdown Tails and wait for the computer to power off 13.249
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.900
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.114
And the file system changes introduced in version 6.3~testoverlayfs are present 0.388
And only the 6.3~testoverlayfs SquashFS delta is installed 0.044
# 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.146
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.238
When the network is plugged 0.020
And Tor is ready 21.986
Then the Upgrader considers the system as up-to-date 0.117
# 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.785
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.400
After features/support/hooks.rb:331 0.855
After features/support/hooks.rb:100 0.013
26.062
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.577
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.216
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.048
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 17.758
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.390
After features/support/hooks.rb:331 0.747
After features/support/hooks.rb:100 0.000