Project Number Date
test_Tails_ISO_stable 5702 08 Jun 2025, 12:32

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 19:37.465 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:20.181
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.168
And I create a 7200 MiB disk named "old" 0.037
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 30.976
When I start Tails from USB drive "old" with network unplugged 1:43.972
Then the boot device has safe access rights 2.970
And Tails is running from USB drive "old" 0.323
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.114
And udev-watchdog is monitoring the correct device 0.319
And I unplug USB drive "old" 0.176
After features/support/hooks.rb:330 8.297
After features/support/hooks.rb:100 0.011
Tags: @product
2:13.750
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login 1:29.534
Then Tails is running from USB drive "old" 0.299
And I create a persistent partition 32.877
And I take note of which tps features are available 1.764
Then a Tails persistence partition exists on USB drive "old" 0.806
And I shutdown Tails and wait for the computer to power off 8.284
After features/support/hooks.rb:330 0.181
After features/support/hooks.rb:100 0.012
Tags: @product
3:1.843
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.171
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.788
Then Tails is running from USB drive "old" 1.412
And all tps features are active 3.143
When I write some files expected to persist 2.718
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.286
And all persistence configuration files have safe access rights 0.447
And all persistent directories from the old Tails version have safe access rights 3.521
And I take note of which tps features are available 0.371
And I shutdown Tails and wait for the computer to power off 4.499
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.481
After features/support/hooks.rb:330 0.153
After features/support/hooks.rb:100 0.007
Tags: @product
2:37.556
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 11.497
And I log in to a new session 21.558
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.983
And I plug USB drive "to_upgrade" 2.508
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.943
Then the running Tails is installed on USB drive "to_upgrade" 24.636
And I unplug USB drive "to_upgrade" 0.198
And I unplug USB drive "__internal" 0.229
After features/support/hooks.rb:330 3.521
After features/support/hooks.rb:100 0.000
Tags: @product
2:1.716
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.318
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:51.400
Then all tps features from the old Tails version are active 1.588
And Tails is running from USB drive "to_upgrade" 0.336
And the boot device has safe access rights 3.424
And the expected persistent files created with the old Tails version are present in the filesystem 1.667
And all persistent directories from the old Tails version have safe access rights 2.980
After features/support/hooks.rb:330 1.339
After features/support/hooks.rb:100 0.012
6:45.355
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.037
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.207
And no SquashFS delta is installed 0.134
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.513
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.262
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.579
When the network is plugged 0.071
And Tor is ready 21.834
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.027
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.209
Given I shutdown Tails and wait for the computer to power off 8.946
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.271
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.349
And the file system changes introduced in version 6.2~testoverlayfs are present 0.313
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.295
# 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.339
When the network is plugged 0.070
And Tor is ready 20.915
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.734
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.896
Given I shutdown Tails and wait for the computer to power off 6.668
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.834
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.008
And the file system changes introduced in version 6.3~testoverlayfs are present 0.493
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.442
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.327
When the network is plugged 0.088
And Tor is ready 18.678
Then the Upgrader considers the system as up-to-date 0.331
# 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 15.721
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.548
After features/support/hooks.rb:330 0.754
After features/support/hooks.rb:100 0.019
37.061
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 11.214
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.570
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.087
And the signing key used by the Upgrader is outdated 0.160
But a current signing key is available on our website 0.000
When the network is plugged 0.076
And Tor is ready 17.990
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.961
After features/support/hooks.rb:330 1.133
After features/support/hooks.rb:100 0.000