Project Number Date
test_Tails_ISO_stable 5627 06 May 2025, 13:33

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 22:21.617 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:54.809
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.331
And I create a 7200 MiB disk named "old" 0.082
And I plug USB drive "old" 1.070
And I write an old version of the Tails USB image to disk "old" 1:11.605
When I start Tails from USB drive "old" with network unplugged 1:37.167
Then the boot device has safe access rights 3.443
And Tails is running from USB drive "old" 0.377
And there is no persistence partition on USB drive "old" 0.088
And process "udev-watchdog" is running 0.112
And udev-watchdog is monitoring the correct device 0.308
And I unplug USB drive "old" 0.221
After features/support/hooks.rb:330 3.950
After features/support/hooks.rb:100 0.011
Tags: @product
2:25.516
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 1.310
And I start Tails from USB drive "old" with network unplugged and I login 1:34.919
Then Tails is running from USB drive "old" 0.462
And I create a persistent partition 36.616
And I take note of which tps features are available 2.719
Then a Tails persistence partition exists on USB drive "old" 0.805
And I shutdown Tails and wait for the computer to power off 8.683
After features/support/hooks.rb:330 0.157
After features/support/hooks.rb:100 0.012
Tags: @product
3:21.384
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.699
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:35.104
Then Tails is running from USB drive "old" 0.429
And all tps features are active 2.784
When I write some files expected to persist 2.027
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.308
And all persistence configuration files have safe access rights 0.513
And all persistent directories from the old Tails version have safe access rights 2.884
And I take note of which tps features are available 0.795
And I shutdown Tails and wait for the computer to power off 6.818
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 29.018
After features/support/hooks.rb:330 0.210
After features/support/hooks.rb:100 0.015
Tags: @product
2:59.716
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 20.206
And I log in to a new session 24.034
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.730
And I plug USB drive "to_upgrade" 2.477
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.709
Then the running Tails is installed on USB drive "to_upgrade" 28.945
And I unplug USB drive "to_upgrade" 0.248
And I unplug USB drive "__internal" 0.363
After features/support/hooks.rb:330 3.415
After features/support/hooks.rb:100 0.000
Tags: @product
2:30.521
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.310
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:19.546
Then all tps features from the old Tails version are active 2.043
And Tails is running from USB drive "to_upgrade" 0.365
And the boot device has safe access rights 3.860
And the expected persistent files created with the old Tails version are present in the filesystem 1.669
And all persistent directories from the old Tails version have safe access rights 2.725
After features/support/hooks.rb:330 1.378
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:30.828
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 23.739
And no SquashFS delta is installed 0.228
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.584
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.120
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.468
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.557
When the network is plugged 0.100
And Tor is ready 24.276
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.031
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.457
Given I shutdown Tails and wait for the computer to power off 11.599
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.049
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.559
And the file system changes introduced in version 6.2~testoverlayfs are present 0.434
And only the 6.2~testoverlayfs SquashFS delta is installed 0.141
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.425
# 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.385
When the network is plugged 0.086
And Tor is ready 21.689
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.303
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.854
Given I shutdown Tails and wait for the computer to power off 4.823
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:20.019
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 3.501
And the file system changes introduced in version 6.3~testoverlayfs are present 0.541
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.357
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.304
When the network is plugged 0.080
And Tor is ready 23.697
Then the Upgrader considers the system as up-to-date 0.370
# 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 17.173
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.756
After features/support/hooks.rb:330 0.737
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
38.839
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 with a persistent partition enabled and logged in 10.871
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.437
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.123
And the signing key used by the Upgrader is outdated 0.128
But a current signing key is available on our website 0.000
When the network is plugged 0.312
And Tor is ready 18.812
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.153
After features/support/hooks.rb:330 1.562
After features/support/hooks.rb:100 0.000