Project Number Date
test_Tails_ISO_stable 5327 11 Dec 2024, 12:46

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 21:15.951 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:35.877
Before features/support/hooks.rb:269 0.006
Given a computer 0.203
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 30.239
When I start Tails from USB drive "old" with network unplugged 2:0.091
Then the boot device has safe access rights 3.202
And Tails is running from USB drive "old" 0.347
And there is no persistence partition on USB drive "old" 0.080
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.304
And I unplug USB drive "old" 0.203
After features/support/hooks.rb:326 8.717
After features/support/hooks.rb:100 0.009
Tags: @product
2:16.536
Before features/support/hooks.rb:269 0.007
Given a computer 0.274
And I start Tails from USB drive "old" with network unplugged and I login 1:30.186
Then Tails is running from USB drive "old" 0.386
And I create a persistent partition 35.903
And I take note of which tps features are available 2.074
Then a Tails persistence partition exists on USB drive "old" 0.930
And I shutdown Tails and wait for the computer to power off 6.779
After features/support/hooks.rb:326 0.178
After features/support/hooks.rb:100 0.009
Tags: @product
3:21.413
Before features/support/hooks.rb:269 0.006
Given a computer 0.246
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:42.979
Then Tails is running from USB drive "old" 0.510
And all tps features are active 2.219
When I write some files expected to persist 2.008
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.219
And all persistence configuration files have safe access rights 0.404
And all persistent directories from the old Tails version have safe access rights 2.479
And I take note of which tps features are available 0.505
And I shutdown Tails and wait for the computer to power off 4.507
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.332
After features/support/hooks.rb:326 0.166
After features/support/hooks.rb:100 0.011
Tags: @product
2:47.843
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.111
And I log in to a new session 19.694
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.874
And I plug USB drive "to_upgrade" 2.490
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.703
Then the running Tails is installed on USB drive "to_upgrade" 30.424
And I unplug USB drive "to_upgrade" 0.273
And I unplug USB drive "__internal" 0.271
After features/support/hooks.rb:326 2.877
After features/support/hooks.rb:100 0.000
Tags: @product
2:30.024
Before features/support/hooks.rb:269 0.014
Given a computer 0.317
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:18.761
Then all tps features from the old Tails version are active 1.917
And Tails is running from USB drive "to_upgrade" 0.368
And the boot device has safe access rights 3.543
And the expected persistent files created with the old Tails version are present in the filesystem 1.984
And all persistent directories from the old Tails version have safe access rights 3.131
After features/support/hooks.rb:326 0.703
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
7:4.378
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 24.675
And no SquashFS delta is installed 0.372
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.386
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.382
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.581
When the network is plugged 0.094
And Tor is ready 23.325
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.518
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.324
Given I shutdown Tails and wait for the computer to power off 11.478
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.310
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.713
And the file system changes introduced in version 6.2~testoverlayfs are present 0.329
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.350
# 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.278
When the network is plugged 0.078
And Tor is ready 21.312
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.575
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.046
Given I shutdown Tails and wait for the computer to power off 4.480
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.117
Then Tails is running version 6.3~testoverlayfs 0.023
And all tps features are active 3.800
And the file system changes introduced in version 6.3~testoverlayfs are present 0.688
And only the 6.3~testoverlayfs SquashFS delta is installed 0.084
# 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.465
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.451
When the network is plugged 0.491
And Tor is ready 18.773
Then the Upgrader considers the system as up-to-date 0.379
# 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.258
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.070
After features/support/hooks.rb:326 0.816
After features/support/hooks.rb:100 0.035
Tags: @product @automatic_upgrade
39.876
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.410
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.621
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.866
But a current signing key is available on our website 0.000
When the network is plugged 0.092
And Tor is ready 18.849
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.970
After features/support/hooks.rb:326 0.794
After features/support/hooks.rb:100 0.000