Project Number Date
test_Tails_ISO_stable 6065 14 Jan 2026, 16:05

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:31.347 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:8.033
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.060
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 14.151
When I start Tails from USB drive "old" with network unplugged 49.216
Then the boot device has safe access rights 2.874
And Tails is running from USB drive "old" 0.263
And there is no persistence partition on USB drive "old" 0.039
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.215
And I unplug USB drive "old" 0.125
After features/support/hooks.rb:331 3.548
After features/support/hooks.rb:100 0.016
Tags: @product
1:27.118
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.054
And I start Tails from USB drive "old" with network unplugged and I login 52.667
Then Tails is running from USB drive "old" 0.247
And I create a persistent partition 24.638
And I take note of which tps features are available 0.649
Then a Tails persistence partition exists on USB drive "old" 0.594
And I shutdown Tails and wait for the computer to power off 8.267
After features/support/hooks.rb:331 0.224
After features/support/hooks.rb:100 0.006
Tags: @product
1:20.496
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.061
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.315
Then Tails is running from USB drive "old" 0.239
And all tps features are active 1.116
When I write some files expected to persist 1.394
# 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.325
And all persistent directories from the old Tails version have safe access rights 1.937
And I take note of which tps features are available 0.144
And I shutdown Tails and wait for the computer to power off 4.061
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.730
After features/support/hooks.rb:331 0.328
After features/support/hooks.rb:100 0.006
Tags: @product
2:9.613
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 without a persistent partition and stopped at Tails Greeter's login screen 8.045
And I log in to a new session 9.983
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.779
And I plug USB drive "to_upgrade" 2.254
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.253
Then the running Tails is installed on USB drive "to_upgrade" 14.987
And I unplug USB drive "to_upgrade" 0.167
And I unplug USB drive "__internal" 0.140
After features/support/hooks.rb:331 3.750
After features/support/hooks.rb:100 0.000
Tags: @product
1:5.905
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 59.423
Then all tps features from the old Tails version are active 0.894
And Tails is running from USB drive "to_upgrade" 0.244
And the boot device has safe access rights 2.522
And the expected persistent files created with the old Tails version are present in the filesystem 1.035
And all persistent directories from the old Tails version have safe access rights 1.734
After features/support/hooks.rb:331 0.812
After features/support/hooks.rb:100 0.006
3:32.587
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.110
And no SquashFS delta is installed 0.058
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.325
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.267
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.341
When the network is plugged 0.015
And Tor is ready 12.907
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.498
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.791
Given I shutdown Tails and wait for the computer to power off 9.328
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.353
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.104
And the file system changes introduced in version 6.2~testoverlayfs are present 0.239
And only the 6.2~testoverlayfs SquashFS delta is installed 0.048
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.143
# 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.207
When the network is plugged 0.014
And Tor is ready 9.715
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.990
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.192
Given I shutdown Tails and wait for the computer to power off 7.891
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.191
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.233
And the file system changes introduced in version 6.3~testoverlayfs are present 0.352
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.186
When the network is plugged 0.013
And Tor is ready 10.690
Then the Upgrader considers the system as up-to-date 10.534
# 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.200
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.381
After features/support/hooks.rb:331 0.802
After features/support/hooks.rb:100 0.010
47.592
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 7.340
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.327
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 0.037
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 39.451
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.371
After features/support/hooks.rb:331 0.597
After features/support/hooks.rb:100 0.000