Project Number Date
test_Tails_ISO_stable 5403 20 Jan 2025, 12: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 19:19.008 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:14.904
Before features/support/hooks.rb:269 0.006
Given a computer 0.254
And I create a 7200 MiB disk named "old" 0.070
And I plug USB drive "old" 1.075
And I write an old version of the Tails USB image to disk "old" 36.110
When I start Tails from USB drive "old" with network unplugged 1:33.373
Then the boot device has safe access rights 3.041
And Tails is running from USB drive "old" 0.312
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.264
And I unplug USB drive "old" 0.237
After features/support/hooks.rb:326 3.553
After features/support/hooks.rb:100 0.010
Tags: @product
2:9.278
Before features/support/hooks.rb:269 0.006
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login 1:28.556
Then Tails is running from USB drive "old" 0.314
And I create a persistent partition 31.392
And I take note of which tps features are available 1.475
Then a Tails persistence partition exists on USB drive "old" 0.963
And I shutdown Tails and wait for the computer to power off 6.393
After features/support/hooks.rb:326 0.161
After features/support/hooks.rb:100 0.008
Tags: @product
2:51.284
Before features/support/hooks.rb:269 0.004
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.396
Then Tails is running from USB drive "old" 1.436
And all tps features are active 2.116
When I write some files expected to persist 1.707
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.246
And all persistence configuration files have safe access rights 0.385
And all persistent directories from the old Tails version have safe access rights 3.669
And I take note of which tps features are available 0.477
And I shutdown Tails and wait for the computer to power off 4.414
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.246
After features/support/hooks.rb:326 0.112
After features/support/hooks.rb:100 0.008
Tags: @product
2:26.157
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.211
And I log in to a new session 18.161
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.574
And I plug USB drive "to_upgrade" 2.480
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.178
Then the running Tails is installed on USB drive "to_upgrade" 18.101
And I unplug USB drive "to_upgrade" 0.215
And I unplug USB drive "__internal" 0.233
After features/support/hooks.rb:326 6.867
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.956
Before features/support/hooks.rb:269 0.006
Given a computer 0.198
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.326
Then all tps features from the old Tails version are active 1.680
And Tails is running from USB drive "to_upgrade" 0.351
And the boot device has safe access rights 3.544
And the expected persistent files created with the old Tails version are present in the filesystem 1.400
And all persistent directories from the old Tails version have safe access rights 2.454
After features/support/hooks.rb:326 1.347
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:40.890
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.043
And no SquashFS delta is installed 0.088
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.325
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.416
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.470
When the network is plugged 0.076
And Tor is ready 19.644
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.719
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.726
Given I shutdown Tails and wait for the computer to power off 8.951
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:25.418
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 2.232
And the file system changes introduced in version 6.2~testoverlayfs are present 0.314
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.291
# 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.312
When the network is plugged 0.075
And Tor is ready 18.299
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.201
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.959
Given I shutdown Tails and wait for the computer to power off 4.316
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.768
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.244
And the file system changes introduced in version 6.3~testoverlayfs are present 0.532
And only the 6.3~testoverlayfs SquashFS delta is installed 0.092
# 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.474
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.440
When the network is plugged 0.075
And Tor is ready 17.411
Then the Upgrader considers the system as up-to-date 0.365
# 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.305
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.124
After features/support/hooks.rb:326 0.872
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
35.536
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.091
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.341
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.061
But a current signing key is available on our website 0.000
When the network is plugged 0.082
And Tor is ready 19.425
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.469
After features/support/hooks.rb:326 1.175
After features/support/hooks.rb:100 0.000