Project Number Date
test_Tails_ISO_stable 5471 19 Feb 2025, 08:47

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:3.655 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:26.871
Before features/support/hooks.rb:269 0.006
Given a computer 0.184
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 33.259
When I start Tails from USB drive "old" with network unplugged 1:47.873
Then the boot device has safe access rights 3.304
And Tails is running from USB drive "old" 0.375
And there is no persistence partition on USB drive "old" 0.110
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.359
And I unplug USB drive "old" 0.204
After features/support/hooks.rb:326 3.724
After features/support/hooks.rb:100 0.008
Tags: @product
2:12.355
Before features/support/hooks.rb:269 0.007
Given a computer 0.224
And I start Tails from USB drive "old" with network unplugged and I login 1:29.073
Then Tails is running from USB drive "old" 0.465
And I create a persistent partition 33.167
And I take note of which tps features are available 1.894
Then a Tails persistence partition exists on USB drive "old" 0.820
And I shutdown Tails and wait for the computer to power off 6.709
After features/support/hooks.rb:326 0.245
After features/support/hooks.rb:100 0.008
Tags: @product
2:57.911
Before features/support/hooks.rb:269 0.005
Given a computer 0.201
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.890
Then Tails is running from USB drive "old" 0.323
And all tps features are active 2.076
When I write some files expected to persist 2.612
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.243
And all persistence configuration files have safe access rights 0.432
And all persistent directories from the old Tails version have safe access rights 2.418
And I take note of which tps features are available 0.499
And I shutdown Tails and wait for the computer to power off 4.357
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.853
After features/support/hooks.rb:326 0.093
After features/support/hooks.rb:100 0.009
Tags: @product
2:36.946
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.165
And I log in to a new session 19.501
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.893
And I plug USB drive "to_upgrade" 2.452
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.209
Then the running Tails is installed on USB drive "to_upgrade" 26.271
And I unplug USB drive "to_upgrade" 0.212
And I unplug USB drive "__internal" 0.240
After features/support/hooks.rb:326 2.503
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.788
Before features/support/hooks.rb:269 0.004
Given a computer 0.232
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.608
Then all tps features from the old Tails version are active 1.791
And Tails is running from USB drive "to_upgrade" 0.359
And the boot device has safe access rights 3.759
And the expected persistent files created with the old Tails version are present in the filesystem 1.517
And all persistent directories from the old Tails version have safe access rights 2.521
After features/support/hooks.rb:326 0.767
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:47.385
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 26.062
And no SquashFS delta is installed 0.087
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.589
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.315
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.458
When the network is plugged 0.062
And Tor is ready 20.925
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.605
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.078
Given I shutdown Tails and wait for the computer to power off 8.964
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.065
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.396
And the file system changes introduced in version 6.2~testoverlayfs are present 0.490
And only the 6.2~testoverlayfs SquashFS delta is installed 0.132
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.324
# 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.292
When the network is plugged 0.089
And Tor is ready 17.823
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.887
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.360
Given I shutdown Tails and wait for the computer to power off 4.459
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.904
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.846
And the file system changes introduced in version 6.3~testoverlayfs are present 1.578
And only the 6.3~testoverlayfs SquashFS delta is installed 0.087
# 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.396
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.314
When the network is plugged 0.062
And Tor is ready 20.001
Then the Upgrader considers the system as up-to-date 0.345
# 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.140
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.131
After features/support/hooks.rb:326 0.757
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
37.396
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.040
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.399
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.065
But a current signing key is available on our website 0.000
When the network is plugged 0.077
And Tor is ready 19.870
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.876
After features/support/hooks.rb:326 1.229
After features/support/hooks.rb:100 0.000