Project Number Date
test_Tails_ISO_stable 5974 27 Nov 2025, 21:34

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 17:15.609 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:29.164
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.204
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.162
And I write an old version of the Tails USB image to disk "old" 47.561
When I start Tails from USB drive "old" with network unplugged 1:36.090
Then the boot device has safe access rights 3.161
And Tails is running from USB drive "old" 0.295
And there is no persistence partition on USB drive "old" 0.089
And process "udev-watchdog" is running 0.072
And udev-watchdog is monitoring the correct device 0.269
And I unplug USB drive "old" 0.210
After features/support/hooks.rb:331 4.139
After features/support/hooks.rb:100 0.013
Tags: @product
2:14.724
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.214
And I start Tails from USB drive "old" with network unplugged and I login 1:33.420
Then Tails is running from USB drive "old" 0.358
And I create a persistent partition 30.791
And I take note of which tps features are available 1.354
Then a Tails persistence partition exists on USB drive "old" 0.836
And I shutdown Tails and wait for the computer to power off 7.748
After features/support/hooks.rb:331 0.365
After features/support/hooks.rb:100 0.012
Tags: @product
2:20.382
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.013
Given a computer 0.172
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:44.897
Then Tails is running from USB drive "old" 0.691
And all tps features are active 2.064
When I write some files expected to persist 1.707
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.224
And all persistence configuration files have safe access rights 0.504
And all persistent directories from the old Tails version have safe access rights 2.575
And I take note of which tps features are available 0.480
And I shutdown Tails and wait for the computer to power off 7.594
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.468
After features/support/hooks.rb:331 0.632
After features/support/hooks.rb:100 0.010
Tags: @product
2:39.620
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 14.373
And I log in to a new session 18.488
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.717
And I plug USB drive "to_upgrade" 2.378
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.473
Then the running Tails is installed on USB drive "to_upgrade" 21.761
And I unplug USB drive "to_upgrade" 0.221
And I unplug USB drive "__internal" 0.204
After features/support/hooks.rb:331 4.123
After features/support/hooks.rb:100 0.000
Tags: @product
1:50.931
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.228
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:41.191
Then all tps features from the old Tails version are active 2.066
And Tails is running from USB drive "to_upgrade" 0.395
And the boot device has safe access rights 3.333
And the expected persistent files created with the old Tails version are present in the filesystem 1.517
And all persistent directories from the old Tails version have safe access rights 2.200
After features/support/hooks.rb:331 1.052
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
5:14.829
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.699
And no SquashFS delta is installed 0.121
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.290
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.357
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.426
When the network is plugged 0.051
And Tor is ready 14.419
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.037
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.169
Given I shutdown Tails and wait for the computer to power off 11.922
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:46.769
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.072
And the file system changes introduced in version 6.2~testoverlayfs are present 0.256
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.167
# 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.298
When the network is plugged 0.085
And Tor is ready 11.923
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.915
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.580
Given I shutdown Tails and wait for the computer to power off 8.247
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:43.133
Then Tails is running version 6.3~testoverlayfs 0.022
And all tps features are active 2.735
And the file system changes introduced in version 6.3~testoverlayfs are present 0.462
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.219
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.249
When the network is plugged 0.055
And Tor is ready 13.355
Then the Upgrader considers the system as up-to-date 0.225
# 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.766
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.583
After features/support/hooks.rb:331 1.046
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
25.956
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 11.184
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.445
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the signing key used by the Upgrader is outdated 0.079
But a current signing key is available on our website 0.000
When the network is plugged 0.060
And Tor is ready 13.443
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.694
After features/support/hooks.rb:331 0.897
After features/support/hooks.rb:100 0.000