Project Number Date
test_Tails_ISO_20979-pdfarranger 8 03 Jun 2025, 03:30

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:55.684 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:0.182
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.201
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 32.231
When I start Tails from USB drive "old" with network unplugged 1:21.495
Then the boot device has safe access rights 3.305
And Tails is running from USB drive "old" 0.973
And there is no persistence partition on USB drive "old" 0.157
And process "udev-watchdog" is running 0.210
And udev-watchdog is monitoring the correct device 0.315
And I unplug USB drive "old" 0.198
After features/support/hooks.rb:330 3.591
After features/support/hooks.rb:100 0.009
Tags: @product
2:25.247
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login 1:40.306
Then Tails is running from USB drive "old" 0.314
And I create a persistent partition 32.965
And I take note of which tps features are available 1.993
Then a Tails persistence partition exists on USB drive "old" 0.862
And I shutdown Tails and wait for the computer to power off 8.609
After features/support/hooks.rb:330 0.136
After features/support/hooks.rb:100 0.007
Tags: @product
3:5.801
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.269
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:29.043
Then Tails is running from USB drive "old" 0.417
And all tps features are active 2.068
When I write some files expected to persist 1.701
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.206
And all persistence configuration files have safe access rights 0.400
And all persistent directories from the old Tails version have safe access rights 2.441
And I take note of which tps features are available 0.679
And I shutdown Tails and wait for the computer to power off 4.309
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.264
After features/support/hooks.rb:330 0.194
After features/support/hooks.rb:100 0.009
Tags: @product
2:35.872
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.891
And I log in to a new session 19.727
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.880
And I plug USB drive "to_upgrade" 2.525
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.919
Then the running Tails is installed on USB drive "to_upgrade" 25.486
And I unplug USB drive "to_upgrade" 0.223
And I unplug USB drive "__internal" 0.216
After features/support/hooks.rb:330 2.091
After features/support/hooks.rb:100 0.000
Tags: @product
2:23.041
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.192
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.473
Then all tps features from the old Tails version are active 1.819
And Tails is running from USB drive "to_upgrade" 0.405
And the boot device has safe access rights 4.058
And the expected persistent files created with the old Tails version are present in the filesystem 1.500
And all persistent directories from the old Tails version have safe access rights 2.591
After features/support/hooks.rb:330 0.755
After features/support/hooks.rb:100 0.010
7:25.413
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.502
And no SquashFS delta is installed 0.522
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.519
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.084
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.443
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.663
When the network is plugged 0.092
And Tor is ready 23.448
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.032
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.612
Given I shutdown Tails and wait for the computer to power off 11.046
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.578
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.370
And the file system changes introduced in version 6.2~testoverlayfs are present 0.389
And only the 6.2~testoverlayfs SquashFS delta is installed 0.088
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.328
# 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.432
When the network is plugged 0.105
And Tor is ready 21.780
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.465
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.984
Given I shutdown Tails and wait for the computer to power off 4.680
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.517
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 1.965
And the file system changes introduced in version 6.3~testoverlayfs are present 0.510
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.287
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.278
When the network is plugged 0.074
And Tor is ready 48.223
Then the Upgrader considers the system as up-to-date 0.310
# 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.948
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.023
After features/support/hooks.rb:330 0.691
After features/support/hooks.rb:100 0.016
1:0.126
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.056
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.103
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.228
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the signing key used by the Upgrader is outdated 0.130
But a current signing key is available on our website 0.000
When the network is plugged 0.087
And Tor is ready 47.848
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.657
After features/support/hooks.rb:330 1.110
After features/support/hooks.rb:100 0.000