Project Number Date
test_Tails_ISO_21373-poweroff-inhibit 28 14 Jun 2026, 20:01

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:32.178 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:11.743
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.014
Given a computer 0.123
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.030
And I write an old version of the Tails USB image to disk "old" 13.039
When I start Tails from USB drive "old" with network unplugged 54.384
Then the boot device has safe access rights 2.394
And Tails is running from USB drive "old" 0.249
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.250
And I unplug USB drive "old" 0.139
After features/support/hooks.rb:339 1.450
After features/support/hooks.rb:108 0.019
Tags: @product
1:25.675
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given a computer 0.113
And I start Tails from USB drive "old" with network unplugged and I login 52.076
Then Tails is running from USB drive "old" 0.301
And I create a persistent partition 24.450
And I take note of which tps features are available 3.868
Then a Tails persistence partition exists on USB drive "old" 0.467
And I shutdown Tails and wait for the computer to power off 4.396
After features/support/hooks.rb:339 0.183
After features/support/hooks.rb:108 0.020
Tags: @product
1:30.038
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given a computer 0.123
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.041
Then Tails is running from USB drive "old" 0.225
And all tps features are active 4.789
When I write some files expected to persist 1.280
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.164
And all persistence configuration files have safe access rights 0.290
And all persistent directories from the old Tails version have safe access rights 1.895
And I take note of which tps features are available 3.711
And I shutdown Tails and wait for the computer to power off 2.726
# 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.787
After features/support/hooks.rb:339 0.323
After features/support/hooks.rb:108 0.018
Tags: @product
2:9.247
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.674
And I log in to a new session 12.346
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.750
And I plug USB drive "to_upgrade" 2.248
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.878
Then the running Tails is installed on USB drive "to_upgrade" 15.077
And I unplug USB drive "to_upgrade" 0.131
And I unplug USB drive "__internal" 0.139
After features/support/hooks.rb:339 2.348
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.919
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.016
Given a computer 0.117
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.044
Then all tps features from the old Tails version are active 1.044
And Tails is running from USB drive "to_upgrade" 0.296
And the boot device has safe access rights 2.475
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.894
After features/support/hooks.rb:339 0.866
After features/support/hooks.rb:108 0.019
Tags: @product @automatic_upgrade
3:44.947
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.014
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.443
And no SquashFS delta is installed 0.065
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.215
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.212
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.411
When the network is plugged 0.015
And Tor is ready 11.819
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.417
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.071
Given I shutdown Tails and wait for the computer to power off 7.305
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.611
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 4.404
And the file system changes introduced in version 6.2~testoverlayfs are present 0.205
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.156
# 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.180
When the network is plugged 0.015
And Tor is ready 9.790
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.761
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.600
Given I shutdown Tails and wait for the computer to power off 4.310
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.132
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.111
And the file system changes introduced in version 6.3~testoverlayfs are present 0.360
And only the 6.3~testoverlayfs SquashFS delta is installed 0.047
# 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.122
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.185
When the network is plugged 0.022
And Tor is ready 10.801
Then the Upgrader considers the system as up-to-date 10.540
# 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.175
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.315
After features/support/hooks.rb:339 0.890
After features/support/hooks.rb:108 0.035
Tags: @product @automatic_upgrade
20.607
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.745
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.299
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.063
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 9.813
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.615
After features/support/hooks.rb:339 0.580
After features/support/hooks.rb:108 0.000