Project Number Date
test_Tails_ISO_stable 6005 12 Dec 2025, 20:39

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 14:16.085 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:51.750
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.043
And I write an old version of the Tails USB image to disk "old" 32.608
When I start Tails from USB drive "old" with network unplugged 1:13.340
Then the boot device has safe access rights 3.587
And Tails is running from USB drive "old" 0.371
And there is no persistence partition on USB drive "old" 0.052
And process "udev-watchdog" is running 0.061
And udev-watchdog is monitoring the correct device 0.281
And I unplug USB drive "old" 0.172
After features/support/hooks.rb:331 3.832
After features/support/hooks.rb:100 0.008
Tags: @product
1:46.519
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login 1:5.383
Then Tails is running from USB drive "old" 0.311
And I create a persistent partition 30.505
And I take note of which tps features are available 1.354
Then a Tails persistence partition exists on USB drive "old" 0.810
And I shutdown Tails and wait for the computer to power off 7.970
After features/support/hooks.rb:331 0.505
After features/support/hooks.rb:100 0.011
Tags: @product
1:50.353
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.215
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:16.170
Then Tails is running from USB drive "old" 0.697
And all tps features are active 1.873
When I write some files expected to persist 1.469
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.200
And all persistence configuration files have safe access rights 0.418
And all persistent directories from the old Tails version have safe access rights 2.253
And I take note of which tps features are available 0.485
And I shutdown Tails and wait for the computer to power off 8.099
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.470
After features/support/hooks.rb:331 0.558
After features/support/hooks.rb:100 0.009
Tags: @product
2:34.492
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 13.057
And I log in to a new session 16.252
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.665
And I plug USB drive "to_upgrade" 2.502
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.421
Then the running Tails is installed on USB drive "to_upgrade" 21.139
And I unplug USB drive "to_upgrade" 0.183
And I unplug USB drive "__internal" 0.268
After features/support/hooks.rb:331 4.176
After features/support/hooks.rb:100 0.000
Tags: @product
1:27.287
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.219
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:17.791
Then all tps features from the old Tails version are active 1.925
And Tails is running from USB drive "to_upgrade" 0.331
And the boot device has safe access rights 3.289
And the expected persistent files created with the old Tails version are present in the filesystem 1.352
And all persistent directories from the old Tails version have safe access rights 2.377
After features/support/hooks.rb:331 0.671
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
4:20.040
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 12.786
And no SquashFS delta is installed 0.130
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.335
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.097
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.314
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.539
When the network is plugged 0.064
And Tor is ready 14.718
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.716
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.859
Given I shutdown Tails and wait for the computer to power off 10.905
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:20.852
Then Tails is running version 6.2~testoverlayfs 0.030
And all tps features are active 2.350
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.110
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.208
# 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.365
When the network is plugged 0.059
And Tor is ready 12.306
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.801
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.468
Given I shutdown Tails and wait for the computer to power off 7.918
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.999
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.170
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.057
# 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.179
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.231
When the network is plugged 0.049
And Tor is ready 12.093
Then the Upgrader considers the system as up-to-date 0.143
# 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.907
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.481
After features/support/hooks.rb:331 1.152
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
25.641
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.369
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.280
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.072
But a current signing key is available on our website 0.000
When the network is plugged 0.082
And Tor is ready 10.864
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.912
After features/support/hooks.rb:331 0.840
After features/support/hooks.rb:100 0.000