Project Number Date
test_Tails_ISO_stable 5768 15 Jul 2025, 18:50

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 29:49.019 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
3:1.628
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.192
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 43.086
When I start Tails from USB drive "old" with network unplugged 2:12.834
Then the boot device has safe access rights 3.356
And Tails is running from USB drive "old" 0.330
And there is no persistence partition on USB drive "old" 0.086
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.337
And I unplug USB drive "old" 0.198
After features/support/hooks.rb:330 4.215
After features/support/hooks.rb:100 0.010
Tags: @product
3:0.721
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.201
And I start Tails from USB drive "old" with network unplugged and I login 2:1.277
Then Tails is running from USB drive "old" 2.761
And I create a persistent partition 42.895
And I take note of which tps features are available 3.616
Then a Tails persistence partition exists on USB drive "old" 1.135
And I shutdown Tails and wait for the computer to power off 8.832
After features/support/hooks.rb:330 0.986
After features/support/hooks.rb:100 0.200
Tags: @product
4:35.115
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.154
Given a computer 1.210
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:33.690
Then Tails is running from USB drive "old" 0.558
And all tps features are active 2.487
When I write some files expected to persist 5.208
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.270
And all persistence configuration files have safe access rights 0.712
And all persistent directories from the old Tails version have safe access rights 5.319
And I take note of which tps features are available 0.489
And I shutdown Tails and wait for the computer to power off 6.650
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 38.518
After features/support/hooks.rb:330 0.138
After features/support/hooks.rb:100 0.011
Tags: @product
3:21.808
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 without a persistent partition and stopped at Tails Greeter's login screen 15.819
And I log in to a new session 24.925
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.930
And I plug USB drive "to_upgrade" 5.035
When I upgrade Tails to USB drive "to_upgrade" by cloning 2:4.386
Then the running Tails is installed on USB drive "to_upgrade" 29.277
And I unplug USB drive "to_upgrade" 0.236
And I unplug USB drive "__internal" 0.197
After features/support/hooks.rb:330 5.590
After features/support/hooks.rb:100 0.000
Tags: @product
3:22.648
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.058
Given a computer 0.528
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:6.001
Then all tps features from the old Tails version are active 2.148
And Tails is running from USB drive "to_upgrade" 0.413
And the boot device has safe access rights 4.164
And the expected persistent files created with the old Tails version are present in the filesystem 2.082
And all persistent directories from the old Tails version have safe access rights 7.308
After features/support/hooks.rb:330 2.879
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
11:29.270
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.013
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 16.191
And no SquashFS delta is installed 0.960
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.265
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.090
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.389
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.506
When the network is plugged 0.086
And Tor is ready 30.130
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 11.896
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 18.861
Given I shutdown Tails and wait for the computer to power off 1:48.481
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:53.592
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 2.620
And the file system changes introduced in version 6.2~testoverlayfs are present 0.355
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.319
# 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.481
When the network is plugged 0.075
And Tor is ready 30.445
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.788
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 17.171
Given I shutdown Tails and wait for the computer to power off 6.831
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:54.996
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 3.117
And the file system changes introduced in version 6.3~testoverlayfs are present 0.732
And only the 6.3~testoverlayfs SquashFS delta is installed 0.125
# 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.346
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.645
When the network is plugged 0.092
And Tor is ready 53.861
Then the Upgrader considers the system as up-to-date 0.410
# 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 24.323
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.968
After features/support/hooks.rb:330 0.773
After features/support/hooks.rb:100 0.039
Tags: @product @automatic_upgrade
57.827
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.020
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 19.297
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.627
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.173
And the signing key used by the Upgrader is outdated 0.692
But a current signing key is available on our website 0.000
When the network is plugged 0.879
And Tor is ready 28.330
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.826
After features/support/hooks.rb:330 0.817
After features/support/hooks.rb:100 0.000