Project Number Date
test_Tails_ISO_stable 5545 02 Apr 2025, 16:58

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 20:29.956 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:14.067
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.213
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.059
And I write an old version of the Tails USB image to disk "old" 32.133
When I start Tails from USB drive "old" with network unplugged 1:36.033
Then the boot device has safe access rights 3.451
And Tails is running from USB drive "old" 0.372
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.122
And udev-watchdog is monitoring the correct device 0.354
And I unplug USB drive "old" 0.208
After features/support/hooks.rb:330 3.790
After features/support/hooks.rb:100 0.014
Tags: @product
2:10.543
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.219
And I start Tails from USB drive "old" with network unplugged and I login 1:27.862
Then Tails is running from USB drive "old" 0.360
And I create a persistent partition 30.337
And I take note of which tps features are available 1.995
Then a Tails persistence partition exists on USB drive "old" 0.968
And I shutdown Tails and wait for the computer to power off 8.799
After features/support/hooks.rb:330 0.235
After features/support/hooks.rb:100 0.012
Tags: @product
2:56.127
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.250
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.016
Then Tails is running from USB drive "old" 0.799
And all tps features are active 2.120
When I write some files expected to persist 1.794
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.227
And all persistence configuration files have safe access rights 0.381
And all persistent directories from the old Tails version have safe access rights 3.120
And I take note of which tps features are available 0.530
And I shutdown Tails and wait for the computer to power off 6.666
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.219
After features/support/hooks.rb:330 0.172
After features/support/hooks.rb:100 0.010
Tags: @product
2:48.670
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.779
And I log in to a new session 23.592
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.585
And I plug USB drive "to_upgrade" 2.573
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.756
Then the running Tails is installed on USB drive "to_upgrade" 26.992
And I unplug USB drive "to_upgrade" 0.191
And I unplug USB drive "__internal" 0.198
After features/support/hooks.rb:330 1.881
After features/support/hooks.rb:100 0.000
Tags: @product
2:33.266
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given a computer 0.268
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:23.234
Then all tps features from the old Tails version are active 1.656
And Tails is running from USB drive "to_upgrade" 0.333
And the boot device has safe access rights 3.629
And the expected persistent files created with the old Tails version are present in the filesystem 1.546
And all persistent directories from the old Tails version have safe access rights 2.596
After features/support/hooks.rb:330 1.781
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:5.766
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 13.184
And no SquashFS delta is installed 0.095
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.654
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.109
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.337
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.618
When the network is plugged 0.118
And Tor is ready 23.326
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.608
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 16.594
Given I shutdown Tails and wait for the computer to power off 11.826
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.455
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.609
And the file system changes introduced in version 6.2~testoverlayfs are present 0.351
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.352
# 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.318
When the network is plugged 0.081
And Tor is ready 19.771
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.098
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.000
Given I shutdown Tails and wait for the computer to power off 4.745
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.789
Then Tails is running version 6.3~testoverlayfs 0.020
And all tps features are active 2.271
And the file system changes introduced in version 6.3~testoverlayfs are present 0.596
And only the 6.3~testoverlayfs SquashFS delta is installed 0.088
# 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.322
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.319
When the network is plugged 0.076
And Tor is ready 20.646
Then the Upgrader considers the system as up-to-date 0.337
# 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 17.278
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.671
After features/support/hooks.rb:330 0.766
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
41.514
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 10.510
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.466
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.114
And the signing key used by the Upgrader is outdated 0.156
But a current signing key is available on our website 0.000
When the network is plugged 0.115
And Tor is ready 23.173
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.975
After features/support/hooks.rb:330 1.194
After features/support/hooks.rb:100 0.000