Project Number Date
test_Tails_ISO_devel 4091 28 Nov 2025, 01: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 17:20.395 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:52.523
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.166
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 35.066
When I start Tails from USB drive "old" with network unplugged 1:12.370
Then the boot device has safe access rights 2.999
And Tails is running from USB drive "old" 0.293
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.045
And udev-watchdog is monitoring the correct device 0.226
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:331 3.897
After features/support/hooks.rb:100 0.010
Tags: @product
2:16.617
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 6.512
And I start Tails from USB drive "old" with network unplugged and I login 1:27.013
Then Tails is running from USB drive "old" 0.306
And I create a persistent partition 30.764
And I take note of which tps features are available 1.274
Then a Tails persistence partition exists on USB drive "old" 0.754
And I shutdown Tails and wait for the computer to power off 9.989
After features/support/hooks.rb:331 0.443
After features/support/hooks.rb:100 0.009
Tags: @product
2:31.146
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 2.666
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:44.682
Then Tails is running from USB drive "old" 0.320
And all tps features are active 14.573
When I write some files expected to persist 1.577
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.180
And all persistence configuration files have safe access rights 0.350
And all persistent directories from the old Tails version have safe access rights 2.189
And I take note of which tps features are available 0.531
And I shutdown Tails and wait for the computer to power off 4.860
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.213
After features/support/hooks.rb:331 0.398
After features/support/hooks.rb:100 0.008
Tags: @product
2:43.959
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.697
And I log in to a new session 17.619
And I clone USB drive "old" to a new USB drive "to_upgrade" 7.586
And I plug USB drive "to_upgrade" 2.387
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.060
Then the running Tails is installed on USB drive "to_upgrade" 22.103
And I unplug USB drive "to_upgrade" 0.264
And I unplug USB drive "__internal" 0.240
After features/support/hooks.rb:331 4.354
After features/support/hooks.rb:100 0.000
Tags: @product
1:51.196
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.226
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:41.711
Then all tps features from the old Tails version are active 1.854
And Tails is running from USB drive "to_upgrade" 0.319
And the boot device has safe access rights 3.022
And the expected persistent files created with the old Tails version are present in the filesystem 1.564
And all persistent directories from the old Tails version have safe access rights 2.499
After features/support/hooks.rb:331 0.814
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
5:39.277
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 with a persistent partition enabled and logged in 14.101
And no SquashFS delta is installed 0.093
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.270
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.332
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.421
When the network is plugged 0.054
And Tor is ready 14.587
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.975
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 16.282
Given I shutdown Tails and wait for the computer to power off 9.599
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.571
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.659
And the file system changes introduced in version 6.2~testoverlayfs are present 0.275
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.150
# 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.290
When the network is plugged 0.052
And Tor is ready 11.720
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.686
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.014
Given I shutdown Tails and wait for the computer to power off 7.871
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:40.827
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.164
And the file system changes introduced in version 6.3~testoverlayfs are present 0.479
And only the 6.3~testoverlayfs SquashFS delta is installed 0.099
# 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.175
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.347
When the network is plugged 0.057
And Tor is ready 12.404
Then the Upgrader considers the system as up-to-date 0.197
# 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.802
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.549
After features/support/hooks.rb:331 1.035
After features/support/hooks.rb:100 0.032
Tags: @product @automatic_upgrade
25.674
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 with a persistent partition enabled and logged in 11.558
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.250
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
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.050
And Tor is ready 11.670
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.034
After features/support/hooks.rb:331 0.828
After features/support/hooks.rb:100 0.000