Project Number Date
test_Tails_ISO_devel 3767 05 Apr 2025, 14:00

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:12.735 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:16.591
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.206
And I create a 7200 MiB disk named "old" 0.055
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 30.829
When I start Tails from USB drive "old" with network unplugged 1:39.739
Then the boot device has safe access rights 3.592
And Tails is running from USB drive "old" 0.418
And there is no persistence partition on USB drive "old" 0.084
And process "udev-watchdog" is running 0.125
And udev-watchdog is monitoring the correct device 0.304
And I unplug USB drive "old" 0.178
After features/support/hooks.rb:330 6.919
After features/support/hooks.rb:100 0.008
Tags: @product
2:16.146
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.232
And I start Tails from USB drive "old" with network unplugged and I login 1:31.400
Then Tails is running from USB drive "old" 0.368
And I create a persistent partition 32.742
And I take note of which tps features are available 1.909
Then a Tails persistence partition exists on USB drive "old" 0.772
And I shutdown Tails and wait for the computer to power off 8.719
After features/support/hooks.rb:330 0.202
After features/support/hooks.rb:100 0.018
Tags: @product
3:4.576
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:26.442
Then Tails is running from USB drive "old" 0.392
And all tps features are active 2.186
When I write some files expected to persist 1.714
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.228
And all persistence configuration files have safe access rights 0.384
And all persistent directories from the old Tails version have safe access rights 2.781
And I take note of which tps features are available 0.463
And I shutdown Tails and wait for the computer to power off 4.589
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.182
After features/support/hooks.rb:330 0.158
After features/support/hooks.rb:100 0.010
Tags: @product
2:39.977
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 14.639
And I log in to a new session 19.600
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.603
And I plug USB drive "to_upgrade" 2.388
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.892
Then the running Tails is installed on USB drive "to_upgrade" 26.372
And I unplug USB drive "to_upgrade" 0.279
And I unplug USB drive "__internal" 0.200
After features/support/hooks.rb:330 6.619
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.189
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.198
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.250
Then all tps features from the old Tails version are active 1.767
And Tails is running from USB drive "to_upgrade" 0.539
And the boot device has safe access rights 3.464
And the expected persistent files created with the old Tails version are present in the filesystem 1.459
And all persistent directories from the old Tails version have safe access rights 2.511
After features/support/hooks.rb:330 1.370
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
6:57.125
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 13.097
And no SquashFS delta is installed 0.106
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.393
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.459
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.633
When the network is plugged 0.066
And Tor is ready 20.975
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.758
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.776
Given I shutdown Tails and wait for the computer to power off 8.865
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.216
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.498
And the file system changes introduced in version 6.2~testoverlayfs are present 0.279
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.409
# 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.289
When the network is plugged 0.082
And Tor is ready 21.585
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.531
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.399
Given I shutdown Tails and wait for the computer to power off 7.121
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.519
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.420
And the file system changes introduced in version 6.3~testoverlayfs are present 0.526
And only the 6.3~testoverlayfs SquashFS delta is installed 0.077
# 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.328
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.320
When the network is plugged 0.068
And Tor is ready 19.524
Then the Upgrader considers the system as up-to-date 0.303
# 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.426
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.893
After features/support/hooks.rb:330 0.751
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
40.127
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.793
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.432
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 0.111
But a current signing key is available on our website 0.000
When the network is plugged 0.073
And Tor is ready 19.932
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.717
After features/support/hooks.rb:330 0.865
After features/support/hooks.rb:100 0.000