Project Number Date
test_Tails_ISO_stable 4925 09 Jul 2024, 17:37

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:10.729 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:46.648
Before features/support/hooks.rb:269 0.006
Given a computer 0.244
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 33.713
When I start Tails from USB drive "old" with network unplugged 2:7.554
Then the boot device has safe access rights 3.036
And Tails is running from USB drive "old" 0.348
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.086
And udev-watchdog is monitoring the correct device 0.306
And I unplug USB drive "old" 0.198
After features/support/hooks.rb:326 7.176
After features/support/hooks.rb:100 0.008
Tags: @product
2:18.137
Before features/support/hooks.rb:269 0.007
Given a computer 0.228
And I start Tails from USB drive "old" with network unplugged and I login 1:35.286
Then Tails is running from USB drive "old" 0.370
And I create a persistent partition 31.194
And I take note of which tps features are available 1.717
Then a Tails persistence partition exists on USB drive "old" 0.796
And I shutdown Tails and wait for the computer to power off 8.541
After features/support/hooks.rb:326 0.204
After features/support/hooks.rb:100 0.011
Tags: @product
2:54.058
Before features/support/hooks.rb:269 0.006
Given a computer 0.223
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.126
Then Tails is running from USB drive "old" 0.434
And all tps features are active 2.112
When I write some files expected to persist 1.683
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.189
And all persistence configuration files have safe access rights 0.436
And all persistent directories from the old Tails version have safe access rights 2.782
And I take note of which tps features are available 0.494
And I shutdown Tails and wait for the computer to power off 4.341
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.234
After features/support/hooks.rb:326 0.167
After features/support/hooks.rb:100 0.011
Tags: @product
2:29.461
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 12.481
And I log in to a new session 17.413
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.526
And I plug USB drive "to_upgrade" 2.469
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.119
Then the running Tails is installed on USB drive "to_upgrade" 19.018
And I unplug USB drive "to_upgrade" 0.222
And I unplug USB drive "__internal" 0.212
After features/support/hooks.rb:326 2.615
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.115
Before features/support/hooks.rb:269 0.008
Given a computer 0.227
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.278
Then all tps features from the old Tails version are active 1.690
And Tails is running from USB drive "to_upgrade" 0.328
And the boot device has safe access rights 3.361
And the expected persistent files created with the old Tails version are present in the filesystem 1.528
And all persistent directories from the old Tails version have safe access rights 2.700
After features/support/hooks.rb:326 0.778
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:50.116
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 12.817
And no SquashFS delta is installed 0.146
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.336
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.370
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.495
When the network is plugged 0.042
And Tor is ready 19.017
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.389
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.190
Given I shutdown Tails and wait for the computer to power off 11.092
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.880
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.605
And the file system changes introduced in version 6.2~testoverlayfs are present 0.333
And only the 6.2~testoverlayfs SquashFS delta is installed 0.082
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.344
# 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.318
When the network is plugged 0.053
And Tor is ready 18.123
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.077
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.305
Given I shutdown Tails and wait for the computer to power off 4.430
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.061
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 3.532
And the file system changes introduced in version 6.3~testoverlayfs are present 0.553
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.424
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.350
When the network is plugged 0.041
And Tor is ready 18.948
Then the Upgrader considers the system as up-to-date 0.330
# 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.178
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.059
After features/support/hooks.rb:326 0.763
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
35.192
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.875
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.347
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.079
And the signing key used by the Upgrader is outdated 0.865
But a current signing key is available on our website 0.000
When the network is plugged 0.046
And Tor is ready 17.534
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.442
After features/support/hooks.rb:326 0.739
After features/support/hooks.rb:100 0.000