Project Number Date
test_Tails_ISO_devel 4110 09 Dec 2025, 17:40

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:51.581 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:2.259
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.191
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.043
And I write an old version of the Tails USB image to disk "old" 30.753
When I start Tails from USB drive "old" with network unplugged 1:26.160
Then the boot device has safe access rights 3.184
And Tails is running from USB drive "old" 0.318
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.243
And I unplug USB drive "old" 0.178
After features/support/hooks.rb:331 3.566
After features/support/hooks.rb:100 0.009
Tags: @product
2:11.184
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login 1:28.237
Then Tails is running from USB drive "old" 0.975
And I create a persistent partition 31.917
And I take note of which tps features are available 1.352
Then a Tails persistence partition exists on USB drive "old" 0.998
And I shutdown Tails and wait for the computer to power off 7.502
After features/support/hooks.rb:331 0.348
After features/support/hooks.rb:100 0.012
Tags: @product
2:23.267
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:45.171
Then Tails is running from USB drive "old" 0.680
And all tps features are active 2.182
When I write some files expected to persist 2.170
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.358
And all persistence configuration files have safe access rights 0.422
And all persistent directories from the old Tails version have safe access rights 4.156
And I take note of which tps features are available 0.627
And I shutdown Tails and wait for the computer to power off 8.089
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.226
After features/support/hooks.rb:331 0.230
After features/support/hooks.rb:100 0.010
Tags: @product
2:46.387
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 10.894
And I log in to a new session 11.682
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.163
And I plug USB drive "to_upgrade" 2.704
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:58.066
Then the running Tails is installed on USB drive "to_upgrade" 21.384
And I unplug USB drive "to_upgrade" 0.251
And I unplug USB drive "__internal" 0.239
After features/support/hooks.rb:331 3.787
After features/support/hooks.rb:100 0.000
Tags: @product
1:32.687
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.200
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:19.847
Then all tps features from the old Tails version are active 2.562
And Tails is running from USB drive "to_upgrade" 0.439
And the boot device has safe access rights 4.644
And the expected persistent files created with the old Tails version are present in the filesystem 1.942
And all persistent directories from the old Tails version have safe access rights 3.050
After features/support/hooks.rb:331 0.972
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
4:33.838
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.177
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.236
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.090
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.291
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.478
When the network is plugged 0.050
And Tor is ready 12.446
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.752
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.807
Given I shutdown Tails and wait for the computer to power off 9.764
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:20.932
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.302
And the file system changes introduced in version 6.2~testoverlayfs are present 0.468
And only the 6.2~testoverlayfs SquashFS delta is installed 0.112
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.164
# 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.236
When the network is plugged 0.059
And Tor is ready 13.255
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.083
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.124
Given I shutdown Tails and wait for the computer to power off 7.838
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:23.577
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 2.803
And the file system changes introduced in version 6.3~testoverlayfs are present 0.627
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.216
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.369
When the network is plugged 0.072
And Tor is ready 13.398
Then the Upgrader considers the system as up-to-date 0.188
# 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 11.268
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.443
After features/support/hooks.rb:331 1.086
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
21.956
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.817
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.485
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.218
And the signing key used by the Upgrader is outdated 0.128
But a current signing key is available on our website 0.000
When the network is plugged 0.067
And Tor is ready 10.625
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.613
After features/support/hooks.rb:331 2.230
After features/support/hooks.rb:100 0.000