Project Number Date
test_Tails_ISO_stable 5982 03 Dec 2025, 21:10

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 16:18.467 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:31.807
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.246
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.042
And I write an old version of the Tails USB image to disk "old" 38.297
When I start Tails from USB drive "old" with network unplugged 1:47.873
Then the boot device has safe access rights 3.303
And Tails is running from USB drive "old" 0.375
And there is no persistence partition on USB drive "old" 0.083
And process "udev-watchdog" is running 0.072
And udev-watchdog is monitoring the correct device 0.245
And I unplug USB drive "old" 0.223
After features/support/hooks.rb:331 3.748
After features/support/hooks.rb:100 0.012
Tags: @product
2:8.363
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.301
And I start Tails from USB drive "old" with network unplugged and I login 1:26.970
Then Tails is running from USB drive "old" 0.713
And I create a persistent partition 29.530
And I take note of which tps features are available 1.562
Then a Tails persistence partition exists on USB drive "old" 0.982
And I shutdown Tails and wait for the computer to power off 8.303
After features/support/hooks.rb:331 0.654
After features/support/hooks.rb:100 0.009
Tags: @product
2:13.646
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:38.746
Then Tails is running from USB drive "old" 0.315
And all tps features are active 1.882
When I write some files expected to persist 1.518
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.203
And all persistence configuration files have safe access rights 0.369
And all persistent directories from the old Tails version have safe access rights 2.321
And I take note of which tps features are available 0.497
And I shutdown Tails and wait for the computer to power off 8.190
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.413
After features/support/hooks.rb:331 0.389
After features/support/hooks.rb:100 0.011
Tags: @product
2:42.240
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.063
And I log in to a new session 16.527
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.418
And I plug USB drive "to_upgrade" 3.372
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:45.245
Then the running Tails is installed on USB drive "to_upgrade" 22.120
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.287
After features/support/hooks.rb:331 3.863
After features/support/hooks.rb:100 0.000
Tags: @product
1:29.287
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.187
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:19.058
Then all tps features from the old Tails version are active 3.318
And Tails is running from USB drive "to_upgrade" 0.345
And the boot device has safe access rights 2.751
And the expected persistent files created with the old Tails version are present in the filesystem 1.318
And all persistent directories from the old Tails version have safe access rights 2.307
After features/support/hooks.rb:331 0.649
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
4:48.832
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 13.836
And no SquashFS delta is installed 0.115
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.276
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.322
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.540
When the network is plugged 0.051
And Tor is ready 16.675
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.551
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.306
Given I shutdown Tails and wait for the computer to power off 14.689
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:36.410
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.332
And the file system changes introduced in version 6.2~testoverlayfs are present 0.283
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.178
# 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.231
When the network is plugged 0.046
And Tor is ready 13.237
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.573
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.003
Given I shutdown Tails and wait for the computer to power off 9.724
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:20.819
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.482
And the file system changes introduced in version 6.3~testoverlayfs are present 0.482
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.203
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.258
When the network is plugged 0.058
And Tor is ready 13.924
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 6.140
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.661
After features/support/hooks.rb:331 0.945
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
24.290
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 10.303
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.299
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the signing key used by the Upgrader is outdated 0.196
But a current signing key is available on our website 0.000
When the network is plugged 0.235
And Tor is ready 11.451
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.732
After features/support/hooks.rb:331 1.066
After features/support/hooks.rb:100 0.000