Project Number Date
test_Tails_ISO_devel 3858 08 Jun 2025, 12:42

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:53.930 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:17.158
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.217
And I create a 7200 MiB disk named "old" 0.059
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 32.278
When I start Tails from USB drive "old" with network unplugged 1:39.299
Then the boot device has safe access rights 3.159
And Tails is running from USB drive "old" 0.356
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.352
And I unplug USB drive "old" 0.214
After features/support/hooks.rb:330 10.180
After features/support/hooks.rb:100 0.008
Tags: @product
2:21.916
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.233
And I start Tails from USB drive "old" with network unplugged and I login 1:36.019
Then Tails is running from USB drive "old" 0.399
And I create a persistent partition 33.474
And I take note of which tps features are available 1.911
Then a Tails persistence partition exists on USB drive "old" 0.915
And I shutdown Tails and wait for the computer to power off 8.961
After features/support/hooks.rb:330 0.218
After features/support/hooks.rb:100 0.009
Tags: @product
3:1.155
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.232
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.365
Then Tails is running from USB drive "old" 0.487
And all tps features are active 2.192
When I write some files expected to persist 1.994
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.281
And all persistence configuration files have safe access rights 0.700
And all persistent directories from the old Tails version have safe access rights 2.725
And I take note of which tps features are available 0.725
And I shutdown Tails and wait for the computer to power off 4.434
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.015
After features/support/hooks.rb:330 0.177
After features/support/hooks.rb:100 0.008
Tags: @product
2:33.909
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 10.677
And I log in to a new session 18.736
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.769
And I plug USB drive "to_upgrade" 3.011
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.788
Then the running Tails is installed on USB drive "to_upgrade" 23.496
And I unplug USB drive "to_upgrade" 0.219
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:330 6.809
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.894
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.212
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.925
Then all tps features from the old Tails version are active 1.683
And Tails is running from USB drive "to_upgrade" 0.327
And the boot device has safe access rights 3.462
And the expected persistent files created with the old Tails version are present in the filesystem 1.660
And all persistent directories from the old Tails version have safe access rights 2.621
After features/support/hooks.rb:330 1.174
After features/support/hooks.rb:100 0.008
7:37.590
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 44.555
And no SquashFS delta is installed 0.094
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.337
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.327
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.503
When the network is plugged 0.067
And Tor is ready 52.702
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.637
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.825
Given I shutdown Tails and wait for the computer to power off 8.620
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.749
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.318
And the file system changes introduced in version 6.2~testoverlayfs are present 0.342
And only the 6.2~testoverlayfs SquashFS delta is installed 0.087
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.350
# 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.297
When the network is plugged 0.067
And Tor is ready 21.187
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.845
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.062
Given I shutdown Tails and wait for the computer to power off 4.592
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.112
Then Tails is running version 6.3~testoverlayfs 0.023
And all tps features are active 2.230
And the file system changes introduced in version 6.3~testoverlayfs are present 0.511
And only the 6.3~testoverlayfs SquashFS delta is installed 0.097
# 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.309
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.294
When the network is plugged 0.093
And Tor is ready 18.452
Then the Upgrader considers the system as up-to-date 0.398
# 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.225
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.177
After features/support/hooks.rb:330 0.649
After features/support/hooks.rb:100 0.017
39.306
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 9.870
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.360
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.089
And the signing key used by the Upgrader is outdated 0.096
But a current signing key is available on our website 0.000
When the network is plugged 0.073
And Tor is ready 20.791
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.023
After features/support/hooks.rb:330 1.327
After features/support/hooks.rb:100 0.000