Project Number Date
test_Tails_ISO_stable 5373 07 Jan 2025, 16:41

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:0.493 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:25.597
Before features/support/hooks.rb:269 0.005
Given a computer 0.214
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 30.553
When I start Tails from USB drive "old" with network unplugged 1:49.459
Then the boot device has safe access rights 3.216
And Tails is running from USB drive "old" 0.329
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.363
And I unplug USB drive "old" 0.198
After features/support/hooks.rb:326 9.994
After features/support/hooks.rb:100 0.010
Tags: @product
2:13.334
Before features/support/hooks.rb:269 0.005
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login 1:28.098
Then Tails is running from USB drive "old" 0.405
And I create a persistent partition 33.322
And I take note of which tps features are available 1.811
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.632
After features/support/hooks.rb:326 0.189
After features/support/hooks.rb:100 0.011
Tags: @product
3:12.953
Before features/support/hooks.rb:269 0.007
Given a computer 0.204
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:33.117
Then Tails is running from USB drive "old" 1.185
And all tps features are active 2.187
When I write some files expected to persist 2.874
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.231
And all persistence configuration files have safe access rights 0.441
And all persistent directories from the old Tails version have safe access rights 3.170
And I take note of which tps features are available 0.594
And I shutdown Tails and wait for the computer to power off 4.495
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.450
After features/support/hooks.rb:326 0.121
After features/support/hooks.rb:100 0.007
Tags: @product
2:30.055
Before features/support/hooks.rb:269 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 10.717
And I log in to a new session 19.295
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.672
And I plug USB drive "to_upgrade" 2.501
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.312
Then the running Tails is installed on USB drive "to_upgrade" 22.124
And I unplug USB drive "to_upgrade" 0.227
And I unplug USB drive "__internal" 0.204
After features/support/hooks.rb:326 2.269
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.663
Before features/support/hooks.rb:269 0.006
Given a computer 0.221
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.881
Then all tps features from the old Tails version are active 1.779
And Tails is running from USB drive "to_upgrade" 0.342
And the boot device has safe access rights 3.317
And the expected persistent files created with the old Tails version are present in the filesystem 1.704
And all persistent directories from the old Tails version have safe access rights 2.416
After features/support/hooks.rb:326 0.717
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:37.326
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 11.912
And no SquashFS delta is installed 0.130
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.393
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.347
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.450
When the network is plugged 0.081
And Tor is ready 23.139
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.839
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.597
Given I shutdown Tails and wait for the computer to power off 11.056
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.996
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 3.094
And the file system changes introduced in version 6.2~testoverlayfs are present 0.301
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.400
# 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.328
When the network is plugged 0.086
And Tor is ready 16.856
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.473
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.980
Given I shutdown Tails and wait for the computer to power off 4.359
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.454
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.998
And the file system changes introduced in version 6.3~testoverlayfs are present 0.524
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.311
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.285
When the network is plugged 0.061
And Tor is ready 21.330
Then the Upgrader considers the system as up-to-date 0.329
# 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 14.941
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.027
After features/support/hooks.rb:326 0.780
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
39.562
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 10.931
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.324
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.088
But a current signing key is available on our website 0.000
When the network is plugged 0.074
And Tor is ready 21.413
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.670
After features/support/hooks.rb:326 0.666
After features/support/hooks.rb:100 0.000