Project Number Date
test_Tails_ISO_stable 5756 03 Jul 2025, 10: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 26:19.396 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:47.429
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.223
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 40.966
When I start Tails from USB drive "old" with network unplugged 1:59.664
Then the boot device has safe access rights 3.760
And Tails is running from USB drive "old" 0.648
And there is no persistence partition on USB drive "old" 0.131
And process "udev-watchdog" is running 0.111
And udev-watchdog is monitoring the correct device 0.631
And I unplug USB drive "old" 0.194
After features/support/hooks.rb:330 4.462
After features/support/hooks.rb:100 0.027
Tags: @product
2:52.122
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.021
Given a computer 0.560
And I start Tails from USB drive "old" with network unplugged and I login 1:54.907
Then Tails is running from USB drive "old" 0.376
And I create a persistent partition 41.153
And I take note of which tps features are available 4.339
Then a Tails persistence partition exists on USB drive "old" 1.446
And I shutdown Tails and wait for the computer to power off 9.338
After features/support/hooks.rb:330 0.201
After features/support/hooks.rb:100 0.013
Tags: @product
4:11.974
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.244
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:13.326
Then Tails is running from USB drive "old" 1.879
And all tps features are active 2.275
When I write some files expected to persist 1.965
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.344
And all persistence configuration files have safe access rights 0.528
And all persistent directories from the old Tails version have safe access rights 3.152
And I take note of which tps features are available 1.689
And I shutdown Tails and wait for the computer to power off 8.013
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 38.554
After features/support/hooks.rb:330 0.212
After features/support/hooks.rb:100 0.036
Tags: @product
3:20.743
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.335
And I log in to a new session 34.054
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.511
And I plug USB drive "to_upgrade" 2.661
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:57.399
Then the running Tails is installed on USB drive "to_upgrade" 33.140
And I unplug USB drive "to_upgrade" 0.365
And I unplug USB drive "__internal" 0.275
After features/support/hooks.rb:330 7.178
After features/support/hooks.rb:100 0.000
Tags: @product
3:4.238
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.272
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:52.570
Then all tps features from the old Tails version are active 2.424
And Tails is running from USB drive "to_upgrade" 0.396
And the boot device has safe access rights 3.438
And the expected persistent files created with the old Tails version are present in the filesystem 1.959
And all persistent directories from the old Tails version have safe access rights 3.176
After features/support/hooks.rb:330 4.581
After features/support/hooks.rb:100 0.034
Tags: @product @automatic_upgrade
9:6.513
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.022
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.324
And no SquashFS delta is installed 1.017
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 2.055
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.336
And the file system changes introduced in version 6.2~testoverlayfs are not present 1.031
And the file system changes introduced in version 6.3~testoverlayfs are not present 1.367
When the network is plugged 0.161
And Tor is ready 27.285
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 12.468
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.712
Given I shutdown Tails and wait for the computer to power off 17.094
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:57.196
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.833
And the file system changes introduced in version 6.2~testoverlayfs are present 0.503
And only the 6.2~testoverlayfs SquashFS delta is installed 0.174
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.334
# 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.358
When the network is plugged 0.073
And Tor is ready 27.055
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.624
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.317
Given I shutdown Tails and wait for the computer to power off 10.205
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:49.520
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 4.616
And the file system changes introduced in version 6.3~testoverlayfs are present 1.631
And only the 6.3~testoverlayfs SquashFS delta is installed 0.465
# 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.727
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.784
When the network is plugged 0.127
And Tor is ready 20.973
Then the Upgrader considers the system as up-to-date 0.395
# 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 21.053
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.652
After features/support/hooks.rb:330 0.784
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
56.374
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.048
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.401
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.161
And the signing key used by the Upgrader is outdated 0.084
But a current signing key is available on our website 0.000
When the network is plugged 0.147
And Tor is ready 26.546
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 12.986
After features/support/hooks.rb:330 2.014
After features/support/hooks.rb:100 0.000