Project Number Date
test_Tails_ISO_devel 3747 21 Mar 2025, 00:03

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 18:33.596 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:2.656
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.148
And I create a 7200 MiB disk named "old" 0.031
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 31.187
When I start Tails from USB drive "old" with network unplugged 1:26.238
Then the boot device has safe access rights 2.983
And Tails is running from USB drive "old" 0.329
And there is no persistence partition on USB drive "old" 0.084
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.303
And I unplug USB drive "old" 0.203
After features/support/hooks.rb:330 3.542
After features/support/hooks.rb:100 0.006
Tags: @product
2:6.351
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.155
And I start Tails from USB drive "old" with network unplugged and I login 1:22.040
Then Tails is running from USB drive "old" 0.303
And I create a persistent partition 33.368
And I take note of which tps features are available 1.386
Then a Tails persistence partition exists on USB drive "old" 0.870
And I shutdown Tails and wait for the computer to power off 8.226
After features/support/hooks.rb:330 0.165
After features/support/hooks.rb:100 0.006
Tags: @product
2:47.249
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.157
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.529
Then Tails is running from USB drive "old" 0.347
And all tps features are active 1.967
When I write some files expected to persist 1.681
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.200
And all persistence configuration files have safe access rights 0.367
And all persistent directories from the old Tails version have safe access rights 2.645
And I take note of which tps features are available 0.362
And I shutdown Tails and wait for the computer to power off 4.591
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.398
After features/support/hooks.rb:330 0.142
After features/support/hooks.rb:100 0.006
Tags: @product
2:30.698
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.948
And I log in to a new session 19.655
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.074
And I plug USB drive "to_upgrade" 2.393
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.623
Then the running Tails is installed on USB drive "to_upgrade" 22.582
And I unplug USB drive "to_upgrade" 0.218
And I unplug USB drive "__internal" 0.200
After features/support/hooks.rb:330 1.909
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.397
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.149
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.186
Then all tps features from the old Tails version are active 1.793
And Tails is running from USB drive "to_upgrade" 0.281
And the boot device has safe access rights 3.099
And the expected persistent files created with the old Tails version are present in the filesystem 1.487
And all persistent directories from the old Tails version have safe access rights 2.399
After features/support/hooks.rb:330 0.773
After features/support/hooks.rb:100 0.006
6:14.138
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.240
And no SquashFS delta is installed 0.099
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.371
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.104
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.430
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.485
When the network is plugged 0.062
And Tor is ready 21.258
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.106
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.311
Given I shutdown Tails and wait for the computer to power off 8.698
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.705
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.045
And the file system changes introduced in version 6.2~testoverlayfs are present 0.270
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.414
# 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.445
When the network is plugged 0.070
And Tor is ready 17.807
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.443
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.278
Given I shutdown Tails and wait for the computer to power off 4.301
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.439
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.101
And the file system changes introduced in version 6.3~testoverlayfs are present 0.500
And only the 6.3~testoverlayfs SquashFS delta is installed 0.093
# 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.321
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.240
When the network is plugged 0.060
And Tor is ready 19.134
Then the Upgrader considers the system as up-to-date 0.292
# 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.040
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.872
After features/support/hooks.rb:330 0.734
After features/support/hooks.rb:100 0.013
34.105
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.090
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.367
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.106
And the signing key used by the Upgrader is outdated 0.127
But a current signing key is available on our website 0.000
When the network is plugged 0.078
And Tor is ready 18.494
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.840
After features/support/hooks.rb:330 0.653
After features/support/hooks.rb:100 0.000