Project Number Date
test_Tails_ISO_stable 5520 18 Mar 2025, 12:58

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:32.146 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:8.869
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.199
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.061
And I write an old version of the Tails USB image to disk "old" 31.028
When I start Tails from USB drive "old" with network unplugged 1:32.363
Then the boot device has safe access rights 3.134
And Tails is running from USB drive "old" 0.319
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.355
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:330 3.866
After features/support/hooks.rb:100 0.073
Tags: @product
2:12.537
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.175
And I start Tails from USB drive "old" with network unplugged and I login 1:29.358
Then Tails is running from USB drive "old" 0.364
And I create a persistent partition 31.641
And I take note of which tps features are available 2.046
Then a Tails persistence partition exists on USB drive "old" 0.737
And I shutdown Tails and wait for the computer to power off 8.213
After features/support/hooks.rb:330 0.172
After features/support/hooks.rb:100 0.008
Tags: @product
2:57.305
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.012
Then Tails is running from USB drive "old" 0.377
And all tps features are active 1.968
When I write some files expected to persist 1.856
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.215
And all persistence configuration files have safe access rights 0.357
And all persistent directories from the old Tails version have safe access rights 2.322
And I take note of which tps features are available 0.457
And I shutdown Tails and wait for the computer to power off 4.341
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.211
After features/support/hooks.rb:330 0.152
After features/support/hooks.rb:100 0.008
Tags: @product
2:35.499
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 9.954
And I log in to a new session 21.076
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.565
And I plug USB drive "to_upgrade" 2.392
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.903
Then the running Tails is installed on USB drive "to_upgrade" 22.185
And I unplug USB drive "to_upgrade" 0.200
And I unplug USB drive "__internal" 0.221
After features/support/hooks.rb:330 2.376
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.213
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.192
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.413
Then all tps features from the old Tails version are active 1.660
And Tails is running from USB drive "to_upgrade" 0.355
And the boot device has safe access rights 3.674
And the expected persistent files created with the old Tails version are present in the filesystem 1.427
And all persistent directories from the old Tails version have safe access rights 2.489
After features/support/hooks.rb:330 0.940
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:47.849
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 10.660
And no SquashFS delta is installed 0.098
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.717
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.112
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.339
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.434
When the network is plugged 0.131
And Tor is ready 41.933
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.592
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.994
Given I shutdown Tails and wait for the computer to power off 10.597
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.542
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.304
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.308
# 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.291
When the network is plugged 0.065
And Tor is ready 16.815
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.558
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.468
Given I shutdown Tails and wait for the computer to power off 4.307
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.933
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 1.933
And the file system changes introduced in version 6.3~testoverlayfs are present 0.535
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.286
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.266
When the network is plugged 0.084
And Tor is ready 17.668
Then the Upgrader considers the system as up-to-date 10.856
# 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.610
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.880
After features/support/hooks.rb:330 0.659
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
37.872
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.236
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.296
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.077
But a current signing key is available on our website 0.000
When the network is plugged 0.077
And Tor is ready 18.118
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.011
After features/support/hooks.rb:330 1.712
After features/support/hooks.rb:100 0.000