Project Number Date
test_Tails_ISO_devel 4138 26 Dec 2025, 11:52

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 15:51.393 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:44.093
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.246
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 27.666
When I start Tails from USB drive "old" with network unplugged 1:10.679
Then the boot device has safe access rights 3.418
And Tails is running from USB drive "old" 0.339
And there is no persistence partition on USB drive "old" 0.081
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.269
And I unplug USB drive "old" 0.202
After features/support/hooks.rb:331 3.793
After features/support/hooks.rb:100 0.023
Tags: @product
1:48.004
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.197
And I start Tails from USB drive "old" with network unplugged and I login 1:7.214
Then Tails is running from USB drive "old" 0.354
And I create a persistent partition 30.004
And I take note of which tps features are available 1.034
Then a Tails persistence partition exists on USB drive "old" 0.706
And I shutdown Tails and wait for the computer to power off 8.492
After features/support/hooks.rb:331 0.612
After features/support/hooks.rb:100 0.010
Tags: @product
1:52.805
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.218
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:15.967
Then Tails is running from USB drive "old" 0.692
And all tps features are active 2.337
When I write some files expected to persist 1.880
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.269
And all persistence configuration files have safe access rights 0.403
And all persistent directories from the old Tails version have safe access rights 2.480
And I take note of which tps features are available 0.472
And I shutdown Tails and wait for the computer to power off 7.827
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 20.255
After features/support/hooks.rb:331 0.689
After features/support/hooks.rb:100 0.012
Tags: @product
2:42.362
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 without a persistent partition and stopped at Tails Greeter's login screen 11.707
And I log in to a new session 10.268
And I clone USB drive "old" to a new USB drive "to_upgrade" 18.523
And I plug USB drive "to_upgrade" 2.245
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.219
Then the running Tails is installed on USB drive "to_upgrade" 20.628
And I unplug USB drive "to_upgrade" 0.194
And I unplug USB drive "__internal" 0.574
After features/support/hooks.rb:331 3.522
After features/support/hooks.rb:100 0.000
Tags: @product
1:32.448
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.233
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:20.200
Then all tps features from the old Tails version are active 2.326
And Tails is running from USB drive "to_upgrade" 0.313
And the boot device has safe access rights 4.634
And the expected persistent files created with the old Tails version are present in the filesystem 1.753
And all persistent directories from the old Tails version have safe access rights 2.987
After features/support/hooks.rb:331 1.080
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
5:20.223
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.871
And no SquashFS delta is installed 0.071
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.262
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.303
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.447
When the network is plugged 0.057
And Tor is ready 43.124
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.575
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.699
Given I shutdown Tails and wait for the computer to power off 5.188
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:24.805
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.445
And the file system changes introduced in version 6.2~testoverlayfs are present 0.312
And only the 6.2~testoverlayfs SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.237
# 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.322
When the network is plugged 0.052
And Tor is ready 42.451
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.612
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.731
Given I shutdown Tails and wait for the computer to power off 3.449
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.145
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.184
And the file system changes introduced in version 6.3~testoverlayfs are present 0.551
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.189
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.311
When the network is plugged 0.070
And Tor is ready 11.871
Then the Upgrader considers the system as up-to-date 10.980
# 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.992
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.672
After features/support/hooks.rb:331 0.879
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
51.456
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 10.495
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.065
And the signing key used by the Upgrader is outdated 0.065
But a current signing key is available on our website 0.000
When the network is plugged 0.088
And Tor is ready 39.874
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.586
After features/support/hooks.rb:331 0.953
After features/support/hooks.rb:100 0.000