Project Number Date
test_Tails_ISO_stable 6309 20 Apr 2026, 11:25

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:25.765 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.317
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.112
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.896
When I start Tails from USB drive "old" with network unplugged 44.446
Then the boot device has safe access rights 3.156
And Tails is running from USB drive "old" 0.246
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.045
And udev-watchdog is monitoring the correct device 0.201
And I unplug USB drive "old" 0.139
After features/support/hooks.rb:331 1.304
After features/support/hooks.rb:100 0.006
Tags: @product
1:29.119
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.058
And I start Tails from USB drive "old" with network unplugged and I login 55.031
Then Tails is running from USB drive "old" 0.264
And I create a persistent partition 24.320
And I take note of which tps features are available 0.645
Then a Tails persistence partition exists on USB drive "old" 0.546
And I shutdown Tails and wait for the computer to power off 8.252
After features/support/hooks.rb:331 0.213
After features/support/hooks.rb:100 0.009
Tags: @product
1:28.487
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given a computer 0.066
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.581
Then Tails is running from USB drive "old" 0.302
And all tps features are active 1.179
When I write some files expected to persist 1.378
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.194
And all persistence configuration files have safe access rights 0.480
And all persistent directories from the old Tails version have safe access rights 1.830
And I take note of which tps features are available 0.173
And I shutdown Tails and wait for the computer to power off 7.882
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.416
After features/support/hooks.rb:331 0.346
After features/support/hooks.rb:100 0.008
Tags: @product
2:11.560
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 without a persistent partition and stopped at Tails Greeter's login screen 7.949
And I log in to a new session 12.899
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.749
And I plug USB drive "to_upgrade" 2.248
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.132
Then the running Tails is installed on USB drive "to_upgrade" 15.284
And I unplug USB drive "to_upgrade" 0.156
And I unplug USB drive "__internal" 0.139
After features/support/hooks.rb:331 2.571
After features/support/hooks.rb:100 0.000
Tags: @product
1:10.425
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.056
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.773
Then all tps features from the old Tails version are active 0.940
And Tails is running from USB drive "to_upgrade" 0.276
And the boot device has safe access rights 2.366
And the expected persistent files created with the old Tails version are present in the filesystem 1.081
And all persistent directories from the old Tails version have safe access rights 1.931
After features/support/hooks.rb:331 0.834
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:37.293
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 with a persistent partition enabled and logged in 8.458
And no SquashFS delta is installed 0.067
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.260
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.285
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.344
When the network is plugged 0.018
And Tor is ready 20.991
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.491
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.212
Given I shutdown Tails and wait for the computer to power off 20.204
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.667
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.247
And the file system changes introduced in version 6.2~testoverlayfs are present 0.216
And only the 6.2~testoverlayfs SquashFS delta is installed 0.042
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.160
# 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.218
When the network is plugged 0.014
And Tor is ready 22.212
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.355
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.205
Given I shutdown Tails and wait for the computer to power off 17.594
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.205
Then Tails is running version 6.3~testoverlayfs 0.024
And all tps features are active 1.126
And the file system changes introduced in version 6.3~testoverlayfs are present 0.426
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.128
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.238
When the network is plugged 0.016
And Tor is ready 20.269
Then the Upgrader considers the system as up-to-date 0.085
# 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.037
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.344
After features/support/hooks.rb:331 0.774
After features/support/hooks.rb:100 0.034
Tags: @product @automatic_upgrade
25.561
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.546
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.249
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the signing key used by the Upgrader is outdated 0.062
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 17.216
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.425
After features/support/hooks.rb:331 0.644
After features/support/hooks.rb:100 0.000