Project Number Date
test_Tails_ISO_devel 3819 18 May 2025, 13:10

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.111 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:22.857
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.013
Given a computer 0.220
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 32.309
When I start Tails from USB drive "old" with network unplugged 1:44.935
Then the boot device has safe access rights 3.190
And Tails is running from USB drive "old" 0.352
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.347
And I unplug USB drive "old" 0.230
After features/support/hooks.rb:330 10.889
After features/support/hooks.rb:100 0.022
Tags: @product
2:16.406
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.217
And I start Tails from USB drive "old" with network unplugged and I login 1:32.124
Then Tails is running from USB drive "old" 0.331
And I create a persistent partition 32.561
And I take note of which tps features are available 1.897
Then a Tails persistence partition exists on USB drive "old" 0.876
And I shutdown Tails and wait for the computer to power off 8.396
After features/support/hooks.rb:330 0.191
After features/support/hooks.rb:100 0.009
Tags: @product
2:59.386
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.834
Then Tails is running from USB drive "old" 0.329
And all tps features are active 2.129
When I write some files expected to persist 1.992
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.353
And all persistence configuration files have safe access rights 0.501
And all persistent directories from the old Tails version have safe access rights 2.496
And I take note of which tps features are available 0.446
And I shutdown Tails and wait for the computer to power off 6.962
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.150
After features/support/hooks.rb:330 0.143
After features/support/hooks.rb:100 0.009
Tags: @product
2:39.158
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.165
And I log in to a new session 22.047
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.866
And I plug USB drive "to_upgrade" 2.483
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.587
Then the running Tails is installed on USB drive "to_upgrade" 26.596
And I unplug USB drive "to_upgrade" 0.193
And I unplug USB drive "__internal" 0.217
After features/support/hooks.rb:330 2.399
After features/support/hooks.rb:100 0.000
Tags: @product
2:23.085
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.234
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.225
Then all tps features from the old Tails version are active 1.790
And Tails is running from USB drive "to_upgrade" 0.383
And the boot device has safe access rights 4.028
And the expected persistent files created with the old Tails version are present in the filesystem 1.657
And all persistent directories from the old Tails version have safe access rights 2.765
After features/support/hooks.rb:330 0.712
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
7:9.119
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 14.704
And no SquashFS delta is installed 0.119
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.398
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.261
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.523
When the network is plugged 0.088
And Tor is ready 18.445
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.852
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.986
Given I shutdown Tails and wait for the computer to power off 9.001
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.522
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.259
And the file system changes introduced in version 6.2~testoverlayfs are present 0.318
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.397
# 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.387
When the network is plugged 0.077
And Tor is ready 21.322
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.827
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.631
Given I shutdown Tails and wait for the computer to power off 4.627
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:17.796
Then Tails is running version 6.3~testoverlayfs 0.021
And all tps features are active 2.622
And the file system changes introduced in version 6.3~testoverlayfs are present 0.572
And only the 6.3~testoverlayfs SquashFS delta is installed 0.083
# 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.344
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.286
When the network is plugged 0.078
And Tor is ready 21.908
Then the Upgrader considers the system as up-to-date 0.323
# 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 16.665
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.513
After features/support/hooks.rb:330 0.809
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
39.097
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 11.869
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.300
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 0.076
But a current signing key is available on our website 0.000
When the network is plugged 0.087
And Tor is ready 19.096
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.601
After features/support/hooks.rb:330 0.761
After features/support/hooks.rb:100 0.000