Project Number Date
test_Tails_ISO_devel 4049 03 Nov 2025, 09:35

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:6.526 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:48.452
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.170
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.040
And I write an old version of the Tails USB image to disk "old" 30.173
When I start Tails from USB drive "old" with network unplugged 1:13.234
Then the boot device has safe access rights 2.910
And Tails is running from USB drive "old" 0.322
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.060
And udev-watchdog is monitoring the correct device 0.259
And I unplug USB drive "old" 0.176
After features/support/hooks.rb:331 3.964
After features/support/hooks.rb:100 0.010
Tags: @product
2:2.285
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 "old" with network unplugged and I login 1:23.151
Then Tails is running from USB drive "old" 0.327
And I create a persistent partition 28.887
And I take note of which tps features are available 1.234
Then a Tails persistence partition exists on USB drive "old" 0.675
And I shutdown Tails and wait for the computer to power off 7.789
After features/support/hooks.rb:331 0.245
After features/support/hooks.rb:100 0.008
Tags: @product
2:11.532
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:38.039
Then Tails is running from USB drive "old" 0.305
And all tps features are active 1.764
When I write some files expected to persist 1.538
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.201
And all persistence configuration files have safe access rights 0.684
And all persistent directories from the old Tails version have safe access rights 2.524
And I take note of which tps features are available 0.432
And I shutdown Tails and wait for the computer to power off 7.665
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.183
After features/support/hooks.rb:331 0.436
After features/support/hooks.rb:100 0.011
Tags: @product
2:36.652
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.797
And I log in to a new session 15.791
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.467
And I plug USB drive "to_upgrade" 4.468
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.350
Then the running Tails is installed on USB drive "to_upgrade" 20.349
And I unplug USB drive "to_upgrade" 0.208
And I unplug USB drive "__internal" 0.219
After features/support/hooks.rb:331 3.740
After features/support/hooks.rb:100 0.000
Tags: @product
1:48.801
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.159
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:38.618
Then all tps features from the old Tails version are active 2.015
And Tails is running from USB drive "to_upgrade" 0.457
And the boot device has safe access rights 3.348
And the expected persistent files created with the old Tails version are present in the filesystem 1.434
And all persistent directories from the old Tails version have safe access rights 2.766
After features/support/hooks.rb:331 0.657
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
5:13.107
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.870
And no SquashFS delta is installed 0.117
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.343
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.318
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.502
When the network is plugged 0.057
And Tor is ready 15.632
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.792
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.932
Given I shutdown Tails and wait for the computer to power off 12.558
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:44.623
Then Tails is running version 6.2~testoverlayfs 0.030
And all tps features are active 5.195
And the file system changes introduced in version 6.2~testoverlayfs are present 0.330
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.189
# 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.339
When the network is plugged 0.082
And Tor is ready 12.089
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.834
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.341
Given I shutdown Tails and wait for the computer to power off 7.810
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:40.943
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.139
And the file system changes introduced in version 6.3~testoverlayfs are present 0.493
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.201
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.263
When the network is plugged 0.060
And Tor is ready 11.956
Then the Upgrader considers the system as up-to-date 0.242
# 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.161
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.460
After features/support/hooks.rb:331 1.149
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
25.696
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.884
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.332
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.080
But a current signing key is available on our website 0.000
When the network is plugged 0.113
And Tor is ready 12.432
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.802
After features/support/hooks.rb:331 1.197
After features/support/hooks.rb:100 0.000