Project Number Date
test_Tails_ISO_stable 5556 05 Apr 2025, 12:45

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.842 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:1.062
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.179
And I create a 7200 MiB disk named "old" 0.040
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 29.074
When I start Tails from USB drive "old" with network unplugged 1:26.670
Then the boot device has safe access rights 3.082
And Tails is running from USB drive "old" 0.300
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.319
And I unplug USB drive "old" 0.177
After features/support/hooks.rb:330 3.510
After features/support/hooks.rb:100 0.009
Tags: @product
2:4.247
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.175
And I start Tails from USB drive "old" with network unplugged and I login 1:21.734
Then Tails is running from USB drive "old" 0.311
And I create a persistent partition 31.149
And I take note of which tps features are available 1.806
Then a Tails persistence partition exists on USB drive "old" 0.809
And I shutdown Tails and wait for the computer to power off 8.261
After features/support/hooks.rb:330 0.131
After features/support/hooks.rb:100 0.009
Tags: @product
2:48.080
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.248
Then Tails is running from USB drive "old" 0.589
And all tps features are active 1.873
When I write some files expected to persist 1.803
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.292
And all persistence configuration files have safe access rights 0.696
And all persistent directories from the old Tails version have safe access rights 2.591
And I take note of which tps features are available 0.392
And I shutdown Tails and wait for the computer to power off 4.382
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.023
After features/support/hooks.rb:330 0.105
After features/support/hooks.rb:100 0.009
Tags: @product
2:25.631
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.067
And I log in to a new session 16.970
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.750
And I plug USB drive "to_upgrade" 2.419
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.794
Then the running Tails is installed on USB drive "to_upgrade" 22.226
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.196
After features/support/hooks.rb:330 1.119
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.277
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.183
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.550
Then all tps features from the old Tails version are active 1.956
And Tails is running from USB drive "to_upgrade" 0.303
And the boot device has safe access rights 3.508
And the expected persistent files created with the old Tails version are present in the filesystem 1.295
And all persistent directories from the old Tails version have safe access rights 2.479
After features/support/hooks.rb:330 1.417
After features/support/hooks.rb:100 0.009
6:21.015
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 with a persistent partition enabled and logged in 11.700
And no SquashFS delta is installed 0.153
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.275
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.289
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.378
When the network is plugged 0.084
And Tor is ready 21.788
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.526
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.688
Given I shutdown Tails and wait for the computer to power off 8.382
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.025
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.003
And the file system changes introduced in version 6.2~testoverlayfs are present 0.373
And only the 6.2~testoverlayfs SquashFS delta is installed 0.101
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.491
# 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.330
When the network is plugged 0.076
And Tor is ready 16.197
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.379
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.573
Given I shutdown Tails and wait for the computer to power off 4.319
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.228
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 1.815
And the file system changes introduced in version 6.3~testoverlayfs are present 0.464
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.299
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.264
When the network is plugged 0.071
And Tor is ready 17.331
Then the Upgrader considers the system as up-to-date 0.306
# 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.542
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.382
After features/support/hooks.rb:330 0.724
After features/support/hooks.rb:100 0.017
36.527
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.161
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.067
And the signing key used by the Upgrader is outdated 0.070
But a current signing key is available on our website 0.000
When the network is plugged 0.065
And Tor is ready 20.713
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.088
After features/support/hooks.rb:330 0.880
After features/support/hooks.rb:100 0.000