Project Number Date
test_Tails_ISO_devel 4142 30 Dec 2025, 12:11

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 13:49.900 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:32.040
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.181
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.043
And I write an old version of the Tails USB image to disk "old" 32.984
When I start Tails from USB drive "old" with network unplugged 53.403
Then the boot device has safe access rights 3.325
And Tails is running from USB drive "old" 0.436
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.049
And udev-watchdog is monitoring the correct device 0.286
And I unplug USB drive "old" 0.203
After features/support/hooks.rb:331 3.947
After features/support/hooks.rb:100 0.009
Tags: @product
1:41.601
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.173
And I start Tails from USB drive "old" with network unplugged and I login 1:2.267
Then Tails is running from USB drive "old" 0.645
And I create a persistent partition 28.570
And I take note of which tps features are available 1.140
Then a Tails persistence partition exists on USB drive "old" 0.802
And I shutdown Tails and wait for the computer to power off 8.001
After features/support/hooks.rb:331 0.341
After features/support/hooks.rb:100 0.008
Tags: @product
1:42.189
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.013
Given a computer 0.176
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:11.965
Then Tails is running from USB drive "old" 0.297
And all tps features are active 1.903
When I write some files expected to persist 1.578
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.198
And all persistence configuration files have safe access rights 0.364
And all persistent directories from the old Tails version have safe access rights 2.164
And I take note of which tps features are available 0.553
And I shutdown Tails and wait for the computer to power off 4.916
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.070
After features/support/hooks.rb:331 0.229
After features/support/hooks.rb:100 0.010
Tags: @product
2:49.807
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.164
And I log in to a new session 16.259
And I clone USB drive "old" to a new USB drive "to_upgrade" 3.464
And I plug USB drive "to_upgrade" 3.005
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:55.819
Then the running Tails is installed on USB drive "to_upgrade" 19.703
And I unplug USB drive "to_upgrade" 0.197
And I unplug USB drive "__internal" 0.194
After features/support/hooks.rb:331 8.622
After features/support/hooks.rb:100 0.000
Tags: @product
1:28.666
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.167
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:20.026
Then all tps features from the old Tails version are active 1.778
And Tails is running from USB drive "to_upgrade" 0.299
And the boot device has safe access rights 2.846
And the expected persistent files created with the old Tails version are present in the filesystem 1.262
And all persistent directories from the old Tails version have safe access rights 2.285
After features/support/hooks.rb:331 0.836
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
4:11.992
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.308
And no SquashFS delta is installed 0.079
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.292
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.267
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.382
When the network is plugged 0.062
And Tor is ready 14.763
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.751
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.292
Given I shutdown Tails and wait for the computer to power off 8.503
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:20.335
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.023
And the file system changes introduced in version 6.2~testoverlayfs are present 0.247
And only the 6.2~testoverlayfs SquashFS delta is installed 0.099
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.185
# 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.194
When the network is plugged 0.050
And Tor is ready 11.810
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.845
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.511
Given I shutdown Tails and wait for the computer to power off 7.547
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.200
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.055
And the file system changes introduced in version 6.3~testoverlayfs are present 0.453
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.181
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.323
When the network is plugged 0.068
And Tor is ready 12.540
Then the Upgrader considers the system as up-to-date 0.101
# 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.858
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.519
After features/support/hooks.rb:331 1.102
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
23.602
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 9.817
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.340
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.104
But a current signing key is available on our website 0.000
When the network is plugged 0.069
And Tor is ready 11.498
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.710
After features/support/hooks.rb:331 0.784
After features/support/hooks.rb:100 0.000