Project Number Date
test_Tails_ISO_stable 6026 29 Dec 2025, 11:49

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:58.133 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:44.886
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.157
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.044
And I write an old version of the Tails USB image to disk "old" 30.645
When I start Tails from USB drive "old" with network unplugged 1:9.179
Then the boot device has safe access rights 2.927
And Tails is running from USB drive "old" 0.303
And there is no persistence partition on USB drive "old" 0.081
And process "udev-watchdog" is running 0.081
And udev-watchdog is monitoring the correct device 0.253
And I unplug USB drive "old" 0.167
After features/support/hooks.rb:331 4.063
After features/support/hooks.rb:100 0.010
Tags: @product
1:39.796
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.163
And I start Tails from USB drive "old" with network unplugged and I login 1:1.734
Then Tails is running from USB drive "old" 0.283
And I create a persistent partition 28.445
And I take note of which tps features are available 1.077
Then a Tails persistence partition exists on USB drive "old" 0.641
And I shutdown Tails and wait for the computer to power off 7.451
After features/support/hooks.rb:331 0.709
After features/support/hooks.rb:100 0.009
Tags: @product
1:35.736
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.214
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:8.415
Then Tails is running from USB drive "old" 0.305
And all tps features are active 1.751
When I write some files expected to persist 1.441
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.173
And all persistence configuration files have safe access rights 0.302
And all persistent directories from the old Tails version have safe access rights 2.140
And I take note of which tps features are available 0.480
And I shutdown Tails and wait for the computer to power off 3.008
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.502
After features/support/hooks.rb:331 0.155
After features/support/hooks.rb:100 0.009
Tags: @product
2:47.041
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.676
And I log in to a new session 15.227
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.341
And I plug USB drive "to_upgrade" 2.438
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:54.813
Then the running Tails is installed on USB drive "to_upgrade" 19.100
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.240
After features/support/hooks.rb:331 3.873
After features/support/hooks.rb:100 0.000
Tags: @product
1:16.172
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.181
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.171
Then all tps features from the old Tails version are active 1.378
And Tails is running from USB drive "to_upgrade" 0.315
And the boot device has safe access rights 2.684
And the expected persistent files created with the old Tails version are present in the filesystem 1.245
And all persistent directories from the old Tails version have safe access rights 2.196
After features/support/hooks.rb:331 0.753
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
4:33.335
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.645
And no SquashFS delta is installed 0.156
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.267
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.262
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.374
When the network is plugged 0.064
And Tor is ready 43.637
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.585
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.071
Given I shutdown Tails and wait for the computer to power off 7.897
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.871
Then Tails is running version 6.2~testoverlayfs 0.043
And all tps features are active 2.025
And the file system changes introduced in version 6.2~testoverlayfs are present 0.274
And only the 6.2~testoverlayfs SquashFS delta is installed 0.058
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.159
# 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.208
When the network is plugged 0.052
And Tor is ready 13.490
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.585
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.118
Given I shutdown Tails and wait for the computer to power off 7.418
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.052
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 1.870
And the file system changes introduced in version 6.3~testoverlayfs are present 0.380
And only the 6.3~testoverlayfs SquashFS delta is installed 0.058
# 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.150
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.210
When the network is plugged 0.048
And Tor is ready 12.438
Then the Upgrader considers the system as up-to-date 0.114
# 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.184
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.471
After features/support/hooks.rb:331 0.638
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
21.164
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.880
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.045
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.053
And Tor is ready 10.283
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.559
After features/support/hooks.rb:331 0.722
After features/support/hooks.rb:100 0.000