Project Number Date
test_Tails_ISO_devel 4040 29 Oct 2025, 09: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:21.332 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:49.539
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.266
And I create a 7200 MiB disk named "old" 0.058
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 25.911
When I start Tails from USB drive "old" with network unplugged 1:18.490
Then the boot device has safe access rights 2.838
And Tails is running from USB drive "old" 0.333
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.247
And I unplug USB drive "old" 0.218
After features/support/hooks.rb:331 3.774
After features/support/hooks.rb:100 0.008
Tags: @product
2:7.992
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login 1:27.329
Then Tails is running from USB drive "old" 0.715
And I create a persistent partition 28.838
And I take note of which tps features are available 1.425
Then a Tails persistence partition exists on USB drive "old" 0.762
And I shutdown Tails and wait for the computer to power off 8.722
After features/support/hooks.rb:331 0.562
After features/support/hooks.rb:100 0.008
Tags: @product
2:11.510
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.224
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:37.012
Then Tails is running from USB drive "old" 0.712
And all tps features are active 2.095
When I write some files expected to persist 1.684
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.214
And all persistence configuration files have safe access rights 0.344
And all persistent directories from the old Tails version have safe access rights 2.239
And I take note of which tps features are available 0.592
And I shutdown Tails and wait for the computer to power off 7.791
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.598
After features/support/hooks.rb:331 0.421
After features/support/hooks.rb:100 0.008
Tags: @product
2:29.509
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 without a persistent partition and stopped at Tails Greeter's login screen 10.300
And I log in to a new session 16.845
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.122
And I plug USB drive "to_upgrade" 2.302
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.509
Then the running Tails is installed on USB drive "to_upgrade" 19.989
And I unplug USB drive "to_upgrade" 0.226
And I unplug USB drive "__internal" 0.212
After features/support/hooks.rb:331 3.968
After features/support/hooks.rb:100 0.000
Tags: @product
1:50.142
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.231
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:40.283
Then all tps features from the old Tails version are active 1.630
And Tails is running from USB drive "to_upgrade" 0.333
And the boot device has safe access rights 3.541
And the expected persistent files created with the old Tails version are present in the filesystem 1.595
And all persistent directories from the old Tails version have safe access rights 2.526
After features/support/hooks.rb:331 0.768
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
5:28.960
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.127
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.305
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.302
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.441
When the network is plugged 0.076
And Tor is ready 15.547
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.583
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.253
Given I shutdown Tails and wait for the computer to power off 9.681
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:40.906
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.226
And the file system changes introduced in version 6.2~testoverlayfs are present 0.301
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.172
# 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.263
When the network is plugged 0.064
And Tor is ready 42.060
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.578
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.194
Given I shutdown Tails and wait for the computer to power off 7.703
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:40.105
Then Tails is running version 6.3~testoverlayfs 0.030
And all tps features are active 2.307
And the file system changes introduced in version 6.3~testoverlayfs are present 0.438
And only the 6.3~testoverlayfs SquashFS delta is installed 0.060
# 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.172
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.246
When the network is plugged 0.067
And Tor is ready 12.545
Then the Upgrader considers the system as up-to-date 0.200
# 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.310
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.476
After features/support/hooks.rb:331 0.783
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
23.677
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.344
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.277
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.115
And the signing key used by the Upgrader is outdated 0.060
But a current signing key is available on our website 0.000
When the network is plugged 0.074
And Tor is ready 11.125
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.678
After features/support/hooks.rb:331 0.876
After features/support/hooks.rb:100 0.000