Project Number Date
test_Tails_ISO_stable 5992 09 Dec 2025, 01:30

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:57.654 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:10.152
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.168
And I create a 7200 MiB disk named "old" 0.197
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 34.102
When I start Tails from USB drive "old" with network unplugged 1:30.367
Then the boot device has safe access rights 3.343
And Tails is running from USB drive "old" 0.340
And there is no persistence partition on USB drive "old" 0.081
And process "udev-watchdog" is running 0.072
And udev-watchdog is monitoring the correct device 0.211
And I unplug USB drive "old" 0.206
After features/support/hooks.rb:331 3.972
After features/support/hooks.rb:100 0.009
Tags: @product
2:10.253
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.172
And I start Tails from USB drive "old" with network unplugged and I login 1:31.328
Then Tails is running from USB drive "old" 0.630
And I create a persistent partition 31.134
And I take note of which tps features are available 1.412
Then a Tails persistence partition exists on USB drive "old" 0.848
And I shutdown Tails and wait for the computer to power off 4.725
After features/support/hooks.rb:331 0.332
After features/support/hooks.rb:100 0.010
Tags: @product
2:11.842
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.172
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:39.827
Then Tails is running from USB drive "old" 0.302
And all tps features are active 1.969
When I write some files expected to persist 1.692
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.225
And all persistence configuration files have safe access rights 0.408
And all persistent directories from the old Tails version have safe access rights 2.173
And I take note of which tps features are available 0.432
And I shutdown Tails and wait for the computer to power off 4.814
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.824
After features/support/hooks.rb:331 0.680
After features/support/hooks.rb:100 0.008
Tags: @product
2:49.996
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 13.269
And I log in to a new session 21.172
And I clone USB drive "old" to a new USB drive "to_upgrade" 3.132
And I plug USB drive "to_upgrade" 3.397
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:45.459
Then the running Tails is installed on USB drive "to_upgrade" 23.138
And I unplug USB drive "to_upgrade" 0.215
And I unplug USB drive "__internal" 0.211
After features/support/hooks.rb:331 4.140
After features/support/hooks.rb:100 0.000
Tags: @product
1:33.951
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.190
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:24.367
Then all tps features from the old Tails version are active 1.921
And Tails is running from USB drive "to_upgrade" 0.384
And the boot device has safe access rights 3.578
And the expected persistent files created with the old Tails version are present in the filesystem 1.328
And all persistent directories from the old Tails version have safe access rights 2.180
After features/support/hooks.rb:331 0.972
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
4:37.511
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 14.015
And no SquashFS delta is installed 0.104
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.068
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.455
When the network is plugged 0.058
And Tor is ready 15.137
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.261
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.362
Given I shutdown Tails and wait for the computer to power off 13.184
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:28.150
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.871
And the file system changes introduced in version 6.2~testoverlayfs are present 0.279
And only the 6.2~testoverlayfs SquashFS delta is installed 0.058
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.163
# 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.273
When the network is plugged 0.057
And Tor is ready 11.635
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.762
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.039
Given I shutdown Tails and wait for the computer to power off 7.996
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:21.331
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.514
And the file system changes introduced in version 6.3~testoverlayfs are present 0.388
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.250
When the network is plugged 0.062
And Tor is ready 13.599
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.925
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.460
After features/support/hooks.rb:331 0.866
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
23.946
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 11.213
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.289
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.068
But a current signing key is available on our website 0.000
When the network is plugged 0.085
And Tor is ready 11.600
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.639
After features/support/hooks.rb:331 1.026
After features/support/hooks.rb:100 0.000