Project Number Date
test_Tails_ISO_stable 5568 11 Apr 2025, 13:16

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:24.605 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.079
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.243
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 31.991
When I start Tails from USB drive "old" with network unplugged 1:36.364
Then the boot device has safe access rights 3.307
And Tails is running from USB drive "old" 0.391
And there is no persistence partition on USB drive "old" 0.112
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.291
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:330 3.528
After features/support/hooks.rb:100 0.008
Tags: @product
2:19.528
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.239
And I start Tails from USB drive "old" with network unplugged and I login 1:29.566
Then Tails is running from USB drive "old" 0.506
And I create a persistent partition 36.803
And I take note of which tps features are available 2.532
Then a Tails persistence partition exists on USB drive "old" 0.953
And I shutdown Tails and wait for the computer to power off 8.926
After features/support/hooks.rb:330 0.247
After features/support/hooks.rb:100 0.011
Tags: @product
3:7.212
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.705
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:25.948
Then Tails is running from USB drive "old" 0.758
And all tps features are active 4.338
When I write some files expected to persist 1.870
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.254
And all persistence configuration files have safe access rights 0.420
And all persistent directories from the old Tails version have safe access rights 2.489
And I take note of which tps features are available 0.488
And I shutdown Tails and wait for the computer to power off 4.454
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.484
After features/support/hooks.rb:330 0.144
After features/support/hooks.rb:100 0.010
Tags: @product
2:42.861
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.275
And I log in to a new session 20.716
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.865
And I plug USB drive "to_upgrade" 2.538
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.083
Then the running Tails is installed on USB drive "to_upgrade" 23.958
And I unplug USB drive "to_upgrade" 0.220
And I unplug USB drive "__internal" 0.201
After features/support/hooks.rb:330 0.933
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.452
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.195
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.931
Then all tps features from the old Tails version are active 1.930
And Tails is running from USB drive "to_upgrade" 0.370
And the boot device has safe access rights 4.139
And the expected persistent files created with the old Tails version are present in the filesystem 1.808
And all persistent directories from the old Tails version have safe access rights 3.075
After features/support/hooks.rb:330 0.994
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
7:0.465
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.554
And no SquashFS delta is installed 1.078
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.460
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.307
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.503
When the network is plugged 0.062
And Tor is ready 22.512
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.064
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.946
Given I shutdown Tails and wait for the computer to power off 8.741
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.040
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 4.761
And the file system changes introduced in version 6.2~testoverlayfs are present 0.326
And only the 6.2~testoverlayfs SquashFS delta is installed 0.090
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.384
# 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.364
When the network is plugged 0.220
And Tor is ready 21.037
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.271
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.900
Given I shutdown Tails and wait for the computer to power off 4.625
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.060
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.078
And the file system changes introduced in version 6.3~testoverlayfs are present 0.486
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.324
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.292
When the network is plugged 0.105
And Tor is ready 21.228
Then the Upgrader considers the system as up-to-date 0.319
# 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.429
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.723
After features/support/hooks.rb:330 0.777
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
40.004
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.748
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.362
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.110
And the signing key used by the Upgrader is outdated 0.130
But a current signing key is available on our website 0.000
When the network is plugged 0.089
And Tor is ready 22.350
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.213
After features/support/hooks.rb:330 0.729
After features/support/hooks.rb:100 0.000