Project Number Date
test_Tails_ISO_stable 6010 17 Dec 2025, 08: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 15:21.418 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
2:0.163
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.183
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.042
And I write an old version of the Tails USB image to disk "old" 33.565
When I start Tails from USB drive "old" with network unplugged 1:20.558
Then the boot device has safe access rights 3.871
And Tails is running from USB drive "old" 0.321
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.059
And udev-watchdog is monitoring the correct device 0.268
And I unplug USB drive "old" 0.182
After features/support/hooks.rb:331 4.018
After features/support/hooks.rb:100 0.011
Tags: @product
1:51.895
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.215
And I start Tails from USB drive "old" with network unplugged and I login 1:10.392
Then Tails is running from USB drive "old" 0.743
And I create a persistent partition 30.511
And I take note of which tps features are available 1.250
Then a Tails persistence partition exists on USB drive "old" 0.635
And I shutdown Tails and wait for the computer to power off 8.146
After features/support/hooks.rb:331 0.202
After features/support/hooks.rb:100 0.008
Tags: @product
1:58.482
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:23.442
Then Tails is running from USB drive "old" 0.669
And all tps features are active 1.824
When I write some files expected to persist 1.558
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.242
And all persistence configuration files have safe access rights 0.384
And all persistent directories from the old Tails version have safe access rights 2.456
And I take note of which tps features are available 0.612
And I shutdown Tails and wait for the computer to power off 7.710
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.394
After features/support/hooks.rb:331 0.568
After features/support/hooks.rb:100 0.012
Tags: @product
2:59.322
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 12.876
And I log in to a new session 17.507
And I clone USB drive "old" to a new USB drive "to_upgrade" 6.933
And I plug USB drive "to_upgrade" 2.579
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:56.456
Then the running Tails is installed on USB drive "to_upgrade" 22.537
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.227
After features/support/hooks.rb:331 3.877
After features/support/hooks.rb:100 0.000
Tags: @product
1:29.686
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.175
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:20.770
Then all tps features from the old Tails version are active 1.722
And Tails is running from USB drive "to_upgrade" 0.293
And the boot device has safe access rights 3.028
And the expected persistent files created with the old Tails version are present in the filesystem 1.407
And all persistent directories from the old Tails version have safe access rights 2.287
After features/support/hooks.rb:331 1.294
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
4:34.696
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 14.205
And no SquashFS delta is installed 0.085
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.297
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.253
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.400
When the network is plugged 0.049
And Tor is ready 15.089
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.699
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.892
Given I shutdown Tails and wait for the computer to power off 10.438
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:26.340
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.205
And the file system changes introduced in version 6.2~testoverlayfs are present 0.327
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.559
# 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.687
When the network is plugged 0.060
And Tor is ready 12.039
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.706
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.176
Given I shutdown Tails and wait for the computer to power off 3.381
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.270
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 9.998
And the file system changes introduced in version 6.3~testoverlayfs are present 0.446
And only the 6.3~testoverlayfs SquashFS delta is installed 0.092
# 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.163
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.264
When the network is plugged 0.996
And Tor is ready 13.607
Then the Upgrader considers the system as up-to-date 0.154
# 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.154
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.489
After features/support/hooks.rb:331 1.231
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
27.172
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 12.478
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.355
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 0.070
But a current signing key is available on our website 0.000
When the network is plugged 0.064
And Tor is ready 12.008
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.131
After features/support/hooks.rb:331 0.746
After features/support/hooks.rb:100 0.000