Project Number Date
test_Tails_ISO_stable 5473 20 Feb 2025, 08:53

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:49.244 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:19.480
Before features/support/hooks.rb:269 0.005
Given a computer 0.228
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.062
And I write an old version of the Tails USB image to disk "old" 31.404
When I start Tails from USB drive "old" with network unplugged 1:42.480
Then the boot device has safe access rights 3.049
And Tails is running from USB drive "old" 0.383
And there is no persistence partition on USB drive "old" 0.081
And process "udev-watchdog" is running 0.087
And udev-watchdog is monitoring the correct device 0.432
And I unplug USB drive "old" 0.224
After features/support/hooks.rb:326 3.817
After features/support/hooks.rb:100 0.010
Tags: @product
2:13.498
Before features/support/hooks.rb:269 0.004
Given a computer 0.221
And I start Tails from USB drive "old" with network unplugged and I login 1:28.638
Then Tails is running from USB drive "old" 0.395
And I create a persistent partition 32.133
And I take note of which tps features are available 2.651
Then a Tails persistence partition exists on USB drive "old" 0.877
And I shutdown Tails and wait for the computer to power off 8.580
After features/support/hooks.rb:326 0.225
After features/support/hooks.rb:100 0.010
Tags: @product
3:6.655
Before features/support/hooks.rb:269 0.006
Given a computer 0.208
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:27.004
Then Tails is running from USB drive "old" 0.320
And all tps features are active 2.401
When I write some files expected to persist 1.832
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.235
And all persistence configuration files have safe access rights 0.492
And all persistent directories from the old Tails version have safe access rights 2.802
And I take note of which tps features are available 0.461
And I shutdown Tails and wait for the computer to power off 6.436
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.459
After features/support/hooks.rb:326 0.160
After features/support/hooks.rb:100 0.035
Tags: @product
2:33.863
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.435
And I log in to a new session 19.226
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.833
And I plug USB drive "to_upgrade" 2.421
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.989
Then the running Tails is installed on USB drive "to_upgrade" 21.528
And I unplug USB drive "to_upgrade" 0.210
And I unplug USB drive "__internal" 0.217
After features/support/hooks.rb:326 7.094
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.166
Before features/support/hooks.rb:269 0.005
Given a computer 0.196
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.485
Then all tps features from the old Tails version are active 1.644
And Tails is running from USB drive "to_upgrade" 0.330
And the boot device has safe access rights 3.659
And the expected persistent files created with the old Tails version are present in the filesystem 1.390
And all persistent directories from the old Tails version have safe access rights 2.458
After features/support/hooks.rb:326 1.126
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:40.471
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 13.130
And no SquashFS delta is installed 0.216
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.346
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.449
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.515
When the network is plugged 0.069
And Tor is ready 21.718
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.073
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.588
Given I shutdown Tails and wait for the computer to power off 8.667
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.741
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.267
And the file system changes introduced in version 6.2~testoverlayfs are present 0.318
And only the 6.2~testoverlayfs SquashFS delta is installed 0.081
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.305
# 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.378
When the network is plugged 0.095
And Tor is ready 21.964
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.536
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.339
Given I shutdown Tails and wait for the computer to power off 4.335
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.785
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.148
And the file system changes introduced in version 6.3~testoverlayfs are present 0.534
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.319
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.278
When the network is plugged 0.074
And Tor is ready 18.964
Then the Upgrader considers the system as up-to-date 0.376
# 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.573
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.097
After features/support/hooks.rb:326 0.861
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
39.107
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 11.879
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.763
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.094
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.091
And Tor is ready 20.675
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.541
After features/support/hooks.rb:326 1.107
After features/support/hooks.rb:100 0.000