Project Number Date
test_Tails_ISO_stable 5307 01 Dec 2024, 12: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 20:48.816 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:29.560
Before features/support/hooks.rb:269 0.004
Given a computer 0.194
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.077
And I write an old version of the Tails USB image to disk "old" 32.101
When I start Tails from USB drive "old" with network unplugged 1:51.583
Then the boot device has safe access rights 3.351
And Tails is running from USB drive "old" 0.392
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.372
And I unplug USB drive "old" 0.278
After features/support/hooks.rb:326 3.554
After features/support/hooks.rb:100 0.053
Tags: @product
2:25.377
Before features/support/hooks.rb:269 0.014
Given a computer 0.241
And I start Tails from USB drive "old" with network unplugged and I login 1:36.770
Then Tails is running from USB drive "old" 0.364
And I create a persistent partition 35.952
And I take note of which tps features are available 1.665
Then a Tails persistence partition exists on USB drive "old" 0.900
And I shutdown Tails and wait for the computer to power off 9.482
After features/support/hooks.rb:326 0.191
After features/support/hooks.rb:100 0.011
Tags: @product
2:55.714
Before features/support/hooks.rb:269 0.008
Given a computer 0.237
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.862
Then Tails is running from USB drive "old" 0.843
And all tps features are active 2.208
When I write some files expected to persist 2.099
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.245
And all persistence configuration files have safe access rights 0.413
And all persistent directories from the old Tails version have safe access rights 2.382
And I take note of which tps features are available 0.453
And I shutdown Tails and wait for the computer to power off 4.479
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.488
After features/support/hooks.rb:326 0.186
After features/support/hooks.rb:100 0.008
Tags: @product
2:34.922
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.335
And I log in to a new session 20.133
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.992
And I plug USB drive "to_upgrade" 2.491
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.517
Then the running Tails is installed on USB drive "to_upgrade" 16.814
And I unplug USB drive "to_upgrade" 0.404
And I unplug USB drive "__internal" 1.233
After features/support/hooks.rb:326 3.626
After features/support/hooks.rb:100 0.000
Tags: @product
2:37.579
Before features/support/hooks.rb:269 0.008
Given a computer 0.238
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:27.017
Then all tps features from the old Tails version are active 1.766
And Tails is running from USB drive "to_upgrade" 0.400
And the boot device has safe access rights 3.783
And the expected persistent files created with the old Tails version are present in the filesystem 1.611
And all persistent directories from the old Tails version have safe access rights 2.762
After features/support/hooks.rb:326 0.740
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:7.108
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 29.283
And no SquashFS delta is installed 0.118
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.401
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.199
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.321
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.540
When the network is plugged 0.199
And Tor is ready 24.420
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.760
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.272
Given I shutdown Tails and wait for the computer to power off 8.947
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:17.326
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 2.505
And the file system changes introduced in version 6.2~testoverlayfs are present 0.373
And only the 6.2~testoverlayfs SquashFS delta is installed 0.102
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.342
# 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.399
When the network is plugged 0.082
And Tor is ready 19.128
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.249
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.760
Given I shutdown Tails and wait for the computer to power off 4.472
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.281
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.126
And the file system changes introduced in version 6.3~testoverlayfs are present 0.488
And only the 6.3~testoverlayfs SquashFS delta is installed 0.089
# 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.361
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.361
When the network is plugged 0.085
And Tor is ready 18.695
Then the Upgrader considers the system as up-to-date 0.366
# 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.966
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.043
After features/support/hooks.rb:326 0.724
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
38.552
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 9.960
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.318
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the signing key used by the Upgrader is outdated 0.818
But a current signing key is available on our website 0.000
When the network is plugged 0.078
And Tor is ready 19.841
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.470
After features/support/hooks.rb:326 0.742
After features/support/hooks.rb:100 0.000