Project Number Date
test_Tails_ISO_stable 5952 14 Nov 2025, 11:17

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:10.932 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:14.710
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.191
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 31.888
When I start Tails from USB drive "old" with network unplugged 1:36.860
Then the boot device has safe access rights 3.649
And Tails is running from USB drive "old" 0.396
And there is no persistence partition on USB drive "old" 0.114
And process "udev-watchdog" is running 0.068
And udev-watchdog is monitoring the correct device 0.263
And I unplug USB drive "old" 0.183
After features/support/hooks.rb:331 3.870
After features/support/hooks.rb:100 0.011
Tags: @product
2:10.416
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login 1:30.110
Then Tails is running from USB drive "old" 0.350
And I create a persistent partition 29.449
And I take note of which tps features are available 1.463
Then a Tails persistence partition exists on USB drive "old" 0.733
And I shutdown Tails and wait for the computer to power off 8.113
After features/support/hooks.rb:331 0.663
After features/support/hooks.rb:100 0.010
Tags: @product
2:15.513
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:41.194
Then Tails is running from USB drive "old" 0.315
And all tps features are active 2.267
When I write some files expected to persist 1.795
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.242
And all persistence configuration files have safe access rights 0.418
And all persistent directories from the old Tails version have safe access rights 2.456
And I take note of which tps features are available 0.556
And I shutdown Tails and wait for the computer to power off 7.677
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.401
After features/support/hooks.rb:331 0.425
After features/support/hooks.rb:100 0.011
Tags: @product
2:46.199
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 13.379
And I log in to a new session 21.540
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.297
And I plug USB drive "to_upgrade" 2.691
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:44.445
Then the running Tails is installed on USB drive "to_upgrade" 21.299
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.341
After features/support/hooks.rb:331 5.751
After features/support/hooks.rb:100 0.000
Tags: @product
1:52.759
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 2.917
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:41.291
Then all tps features from the old Tails version are active 1.794
And Tails is running from USB drive "to_upgrade" 0.275
And the boot device has safe access rights 2.792
And the expected persistent files created with the old Tails version are present in the filesystem 1.392
And all persistent directories from the old Tails version have safe access rights 2.296
After features/support/hooks.rb:331 0.632
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
4:59.268
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 13.297
And no SquashFS delta is installed 0.105
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.253
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.286
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.385
When the network is plugged 0.048
And Tor is ready 13.762
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.778
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.792
Given I shutdown Tails and wait for the computer to power off 10.938
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:40.217
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.220
And the file system changes introduced in version 6.2~testoverlayfs are present 0.243
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.147
# 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.238
When the network is plugged 0.058
And Tor is ready 12.533
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.584
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.080
Given I shutdown Tails and wait for the computer to power off 7.504
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:38.089
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.196
And the file system changes introduced in version 6.3~testoverlayfs are present 0.514
And only the 6.3~testoverlayfs SquashFS delta is installed 0.089
# 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.170
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.260
When the network is plugged 0.060
And Tor is ready 13.863
Then the Upgrader considers the system as up-to-date 0.188
# 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.610
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.594
After features/support/hooks.rb:331 0.934
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
52.064
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.551
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.286
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.080
But a current signing key is available on our website 0.000
When the network is plugged 0.052
And Tor is ready 40.460
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.568
After features/support/hooks.rb:331 0.795
After features/support/hooks.rb:100 0.000