Project Number Date
test_Tails_ISO_stable 6282 09 Apr 2026, 11: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 13:4.828 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:3.651
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.052
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 14.209
When I start Tails from USB drive "old" with network unplugged 44.386
Then the boot device has safe access rights 3.179
And Tails is running from USB drive "old" 0.253
And there is no persistence partition on USB drive "old" 0.045
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.232
And I unplug USB drive "old" 0.208
After features/support/hooks.rb:331 3.532
After features/support/hooks.rb:100 0.051
Tags: @product
1:32.584
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 57.406
Then Tails is running from USB drive "old" 0.323
And I create a persistent partition 25.015
And I take note of which tps features are available 0.843
Then a Tails persistence partition exists on USB drive "old" 0.665
And I shutdown Tails and wait for the computer to power off 8.271
After features/support/hooks.rb:331 0.305
After features/support/hooks.rb:100 0.008
Tags: @product
1:32.296
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.856
Then Tails is running from USB drive "old" 0.297
And all tps features are active 1.333
When I write some files expected to persist 1.416
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.167
And all persistence configuration files have safe access rights 0.492
And all persistent directories from the old Tails version have safe access rights 2.073
And I take note of which tps features are available 0.191
And I shutdown Tails and wait for the computer to power off 8.039
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.352
After features/support/hooks.rb:331 0.546
After features/support/hooks.rb:100 0.008
Tags: @product
2:20.255
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 without a persistent partition and stopped at Tails Greeter's login screen 8.509
And I log in to a new session 18.859
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.857
And I plug USB drive "to_upgrade" 2.262
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.548
Then the running Tails is installed on USB drive "to_upgrade" 16.774
And I unplug USB drive "to_upgrade" 0.143
And I unplug USB drive "__internal" 0.300
After features/support/hooks.rb:331 2.585
After features/support/hooks.rb:100 0.000
Tags: @product
1:16.824
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.071
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.724
Then all tps features from the old Tails version are active 1.480
And Tails is running from USB drive "to_upgrade" 0.395
And the boot device has safe access rights 3.321
And the expected persistent files created with the old Tails version are present in the filesystem 1.528
And all persistent directories from the old Tails version have safe access rights 2.303
After features/support/hooks.rb:331 0.918
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
4:48.009
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.049
And no SquashFS delta is installed 0.088
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.326
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.290
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.475
When the network is plugged 0.053
And Tor is ready 22.608
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.388
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.335
Given I shutdown Tails and wait for the computer to power off 20.781
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.965
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.307
And the file system changes introduced in version 6.2~testoverlayfs are present 0.283
And only the 6.2~testoverlayfs SquashFS delta is installed 0.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.157
# 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.227
When the network is plugged 0.037
And Tor is ready 22.311
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.422
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.659
Given I shutdown Tails and wait for the computer to power off 18.371
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.070
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.184
And the file system changes introduced in version 6.3~testoverlayfs are present 0.331
And only the 6.3~testoverlayfs SquashFS delta is installed 0.039
# 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.149
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.214
When the network is plugged 0.017
And Tor is ready 22.344
Then the Upgrader considers the system as up-to-date 0.103
# 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.901
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.389
After features/support/hooks.rb:331 1.094
After features/support/hooks.rb:100 0.032
Tags: @product @automatic_upgrade
31.204
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.162
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.263
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.081
But a current signing key is available on our website 0.000
When the network is plugged 0.028
And Tor is ready 22.214
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.402
After features/support/hooks.rb:331 1.044
After features/support/hooks.rb:100 0.000