Project Number Date
test_Tails_ISO_devel 3720 04 Mar 2025, 17:35

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 19:31.682 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:13.308
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.187
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.059
And I write an old version of the Tails USB image to disk "old" 33.473
When I start Tails from USB drive "old" with network unplugged 1:34.187
Then the boot device has safe access rights 3.323
And Tails is running from USB drive "old" 0.335
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.332
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:330 3.544
After features/support/hooks.rb:100 0.022
Tags: @product
2:17.167
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.235
And I start Tails from USB drive "old" with network unplugged and I login 1:31.930
Then Tails is running from USB drive "old" 0.308
And I create a persistent partition 31.549
And I take note of which tps features are available 1.577
Then a Tails persistence partition exists on USB drive "old" 0.836
And I shutdown Tails and wait for the computer to power off 10.728
After features/support/hooks.rb:330 0.271
After features/support/hooks.rb:100 0.009
Tags: @product
2:56.613
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.235
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.586
Then Tails is running from USB drive "old" 0.441
And all tps features are active 2.022
When I write some files expected to persist 2.062
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.264
And all persistence configuration files have safe access rights 0.412
And all persistent directories from the old Tails version have safe access rights 2.739
And I take note of which tps features are available 0.599
And I shutdown Tails and wait for the computer to power off 4.484
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.763
After features/support/hooks.rb:330 0.125
After features/support/hooks.rb:100 0.012
Tags: @product
2:25.802
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 without a persistent partition and stopped at Tails Greeter's login screen 11.216
And I log in to a new session 18.623
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.713
And I plug USB drive "to_upgrade" 2.416
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.473
Then the running Tails is installed on USB drive "to_upgrade" 17.937
And I unplug USB drive "to_upgrade" 0.197
And I unplug USB drive "__internal" 0.223
After features/support/hooks.rb:330 2.503
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.174
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.199
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.586
Then all tps features from the old Tails version are active 1.758
And Tails is running from USB drive "to_upgrade" 0.364
And the boot device has safe access rights 3.513
And the expected persistent files created with the old Tails version are present in the filesystem 1.952
And all persistent directories from the old Tails version have safe access rights 2.799
After features/support/hooks.rb:330 1.087
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:41.201
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 12.336
And no SquashFS delta is installed 0.153
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.389
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.094
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.563
And the file system changes introduced in version 6.3~testoverlayfs are not present 1.173
When the network is plugged 0.083
And Tor is ready 19.961
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.243
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.333
Given I shutdown Tails and wait for the computer to power off 8.716
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.883
Then Tails is running version 6.2~testoverlayfs 0.021
And all tps features are active 2.264
And the file system changes introduced in version 6.2~testoverlayfs are present 0.326
And only the 6.2~testoverlayfs SquashFS delta is installed 0.120
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.318
# 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.494
When the network is plugged 0.077
And Tor is ready 19.887
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.792
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.947
Given I shutdown Tails and wait for the computer to power off 4.401
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.054
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 4.957
And the file system changes introduced in version 6.3~testoverlayfs are present 0.529
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.359
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.364
When the network is plugged 0.556
And Tor is ready 21.780
Then the Upgrader considers the system as up-to-date 0.332
# 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.468
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.124
After features/support/hooks.rb:330 0.801
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
38.415
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.079
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.858
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.107
But a current signing key is available on our website 0.000
When the network is plugged 0.097
And Tor is ready 20.599
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.612
After features/support/hooks.rb:330 0.723
After features/support/hooks.rb:100 0.000