Project Number Date
test_Tails_ISO_stable 5977 30 Nov 2025, 17:59

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:34.667 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:1.396
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.170
Given a computer 0.270
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.071
And I write an old version of the Tails USB image to disk "old" 32.595
When I start Tails from USB drive "old" with network unplugged 1:23.049
Then the boot device has safe access rights 3.415
And Tails is running from USB drive "old" 0.344
And there is no persistence partition on USB drive "old" 0.059
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.220
After features/support/hooks.rb:331 4.296
After features/support/hooks.rb:100 0.009
Tags: @product
2:8.685
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login 1:24.652
Then Tails is running from USB drive "old" 0.290
And I create a persistent partition 29.248
And I take note of which tps features are available 3.498
Then a Tails persistence partition exists on USB drive "old" 3.008
And I shutdown Tails and wait for the computer to power off 7.797
After features/support/hooks.rb:331 0.349
After features/support/hooks.rb:100 0.008
Tags: @product
2:11.894
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:37.785
Then Tails is running from USB drive "old" 0.347
And all tps features are active 1.850
When I write some files expected to persist 1.711
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.208
And all persistence configuration files have safe access rights 0.375
And all persistent directories from the old Tails version have safe access rights 2.644
And I take note of which tps features are available 0.604
And I shutdown Tails and wait for the computer to power off 7.761
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.403
After features/support/hooks.rb:331 0.499
After features/support/hooks.rb:100 0.009
Tags: @product
2:47.994
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 14.712
And I log in to a new session 16.650
And I clone USB drive "old" to a new USB drive "to_upgrade" 7.677
And I plug USB drive "to_upgrade" 2.487
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:44.088
Then the running Tails is installed on USB drive "to_upgrade" 21.985
And I unplug USB drive "to_upgrade" 0.183
And I unplug USB drive "__internal" 0.210
After features/support/hooks.rb:331 4.040
After features/support/hooks.rb:100 0.000
Tags: @product
1:57.040
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.189
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:48.262
Then all tps features from the old Tails version are active 1.411
And Tails is running from USB drive "to_upgrade" 0.322
And the boot device has safe access rights 3.092
And the expected persistent files created with the old Tails version are present in the filesystem 1.380
And all persistent directories from the old Tails version have safe access rights 2.381
After features/support/hooks.rb:331 0.959
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
5:3.223
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 14.097
And no SquashFS delta is installed 0.100
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.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.272
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.433
When the network is plugged 0.079
And Tor is ready 15.353
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.975
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.114
Given I shutdown Tails and wait for the computer to power off 11.397
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:40.731
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 1.981
And the file system changes introduced in version 6.2~testoverlayfs are present 0.289
And only the 6.2~testoverlayfs SquashFS delta is installed 0.076
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.161
# 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.228
When the network is plugged 0.053
And Tor is ready 13.295
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.597
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.518
Given I shutdown Tails and wait for the computer to power off 7.713
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:36.947
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.222
And the file system changes introduced in version 6.3~testoverlayfs are present 0.509
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.198
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.301
When the network is plugged 0.065
And Tor is ready 12.647
Then the Upgrader considers the system as up-to-date 0.194
# 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.749
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.491
After features/support/hooks.rb:331 0.932
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
24.432
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.356
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.306
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the signing key used by the Upgrader is outdated 0.070
But a current signing key is available on our website 0.000
When the network is plugged 0.050
And Tor is ready 12.038
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.566
After features/support/hooks.rb:331 1.408
After features/support/hooks.rb:100 0.000