Project Number Date
test_Tails_ISO_stable 6316 21 Apr 2026, 16:17

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:54.625 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:23.089
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.081
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.031
And I write an old version of the Tails USB image to disk "old" 15.384
When I start Tails from USB drive "old" with network unplugged 1:2.387
Then the boot device has safe access rights 3.292
And Tails is running from USB drive "old" 0.273
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.070
And udev-watchdog is monitoring the correct device 0.273
And I unplug USB drive "old" 0.227
After features/support/hooks.rb:331 1.812
After features/support/hooks.rb:100 0.007
Tags: @product
1:29.989
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.065
And I start Tails from USB drive "old" with network unplugged and I login 57.138
Then Tails is running from USB drive "old" 0.249
And I create a persistent partition 26.711
And I take note of which tps features are available 0.917
Then a Tails persistence partition exists on USB drive "old" 0.656
And I shutdown Tails and wait for the computer to power off 4.251
After features/support/hooks.rb:331 0.413
After features/support/hooks.rb:100 0.007
Tags: @product
1:33.010
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.054
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:8.355
Then Tails is running from USB drive "old" 0.330
And all tps features are active 1.650
When I write some files expected to persist 1.563
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.228
And all persistence configuration files have safe access rights 0.489
And all persistent directories from the old Tails version have safe access rights 2.286
And I take note of which tps features are available 0.226
And I shutdown Tails and wait for the computer to power off 4.252
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.571
After features/support/hooks.rb:331 0.423
After features/support/hooks.rb:100 0.015
Tags: @product
2:20.530
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.505
And I log in to a new session 17.641
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.844
And I plug USB drive "to_upgrade" 2.247
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.297
Then the running Tails is installed on USB drive "to_upgrade" 17.706
And I unplug USB drive "to_upgrade" 0.149
And I unplug USB drive "__internal" 0.138
After features/support/hooks.rb:331 3.841
After features/support/hooks.rb:100 0.000
Tags: @product
1:18.664
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.094
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:10.192
Then all tps features from the old Tails version are active 1.322
And Tails is running from USB drive "to_upgrade" 0.452
And the boot device has safe access rights 2.922
And the expected persistent files created with the old Tails version are present in the filesystem 1.419
And all persistent directories from the old Tails version have safe access rights 2.260
After features/support/hooks.rb:331 0.719
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
5:20.845
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.848
And no SquashFS delta is installed 0.080
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.362
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.226
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.396
When the network is plugged 0.014
And Tor is ready 45.722
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.452
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.383
Given I shutdown Tails and wait for the computer to power off 19.645
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:20.327
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.300
And the file system changes introduced in version 6.2~testoverlayfs are present 0.244
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.163
# 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.221
When the network is plugged 0.018
And Tor is ready 22.583
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.462
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.929
Given I shutdown Tails and wait for the computer to power off 12.686
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:22.024
Then Tails is running version 6.3~testoverlayfs 0.009
And all tps features are active 1.875
And the file system changes introduced in version 6.3~testoverlayfs are present 0.538
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.157
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.287
When the network is plugged 0.020
And Tor is ready 22.604
Then the Upgrader considers the system as up-to-date 0.149
# 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 5.501
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.423
After features/support/hooks.rb:331 0.816
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
28.494
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.779
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.286
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.043
But a current signing key is available on our website 0.000
When the network is plugged 0.027
And Tor is ready 19.870
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.428
After features/support/hooks.rb:331 1.169
After features/support/hooks.rb:100 0.000