Project Number Date
test_Tails_ISO_stable 5651 16 May 2025, 12:54

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:56.300 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.419
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.281
And I create a 7200 MiB disk named "old" 0.057
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 29.567
When I start Tails from USB drive "old" with network unplugged 1:44.072
Then the boot device has safe access rights 3.286
And Tails is running from USB drive "old" 0.378
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.101
And udev-watchdog is monitoring the correct device 0.364
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:330 3.765
After features/support/hooks.rb:100 0.010
Tags: @product
2:24.300
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login 1:43.938
Then Tails is running from USB drive "old" 0.359
And I create a persistent partition 30.206
And I take note of which tps features are available 2.164
Then a Tails persistence partition exists on USB drive "old" 0.829
And I shutdown Tails and wait for the computer to power off 6.602
After features/support/hooks.rb:330 0.181
After features/support/hooks.rb:100 0.026
Tags: @product
3:13.863
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.021
Given a computer 0.262
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:32.762
Then Tails is running from USB drive "old" 0.431
And all tps features are active 2.889
When I write some files expected to persist 2.011
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.242
And all persistence configuration files have safe access rights 0.426
And all persistent directories from the old Tails version have safe access rights 2.678
And I take note of which tps features are available 1.211
And I shutdown Tails and wait for the computer to power off 6.404
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.542
After features/support/hooks.rb:330 0.170
After features/support/hooks.rb:100 0.013
Tags: @product
2:45.828
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 11.851
And I log in to a new session 19.384
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.572
And I plug USB drive "to_upgrade" 2.478
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:45.360
Then the running Tails is installed on USB drive "to_upgrade" 24.736
And I unplug USB drive "to_upgrade" 0.226
And I unplug USB drive "__internal" 0.218
After features/support/hooks.rb:330 3.041
After features/support/hooks.rb:100 0.000
Tags: @product
2:29.291
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.249
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:18.857
Then all tps features from the old Tails version are active 1.783
And Tails is running from USB drive "to_upgrade" 0.371
And the boot device has safe access rights 3.612
And the expected persistent files created with the old Tails version are present in the filesystem 1.718
And all persistent directories from the old Tails version have safe access rights 2.699
After features/support/hooks.rb:330 1.440
After features/support/hooks.rb:100 0.031
Tags: @product @automatic_upgrade
7:2.425
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 11.885
And no SquashFS delta is installed 0.118
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.966
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.433
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.404
When the network is plugged 0.085
And Tor is ready 20.421
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.922
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.783
Given I shutdown Tails and wait for the computer to power off 11.351
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.603
Then Tails is running version 6.2~testoverlayfs 0.040
And all tps features are active 2.594
And the file system changes introduced in version 6.2~testoverlayfs are present 0.366
And only the 6.2~testoverlayfs SquashFS delta is installed 0.120
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.337
# 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.314
When the network is plugged 0.080
And Tor is ready 17.486
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.096
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.215
Given I shutdown Tails and wait for the computer to power off 6.713
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.074
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.231
And the file system changes introduced in version 6.3~testoverlayfs are present 0.627
And only the 6.3~testoverlayfs SquashFS delta is installed 0.101
# 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.554
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.498
When the network is plugged 0.094
And Tor is ready 20.366
Then the Upgrader considers the system as up-to-date 0.362
# 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 16.078
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.023
After features/support/hooks.rb:330 0.823
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
41.171
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 with a persistent partition enabled and logged in 11.046
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.446
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.100
And the signing key used by the Upgrader is outdated 0.197
But a current signing key is available on our website 0.000
When the network is plugged 0.105
And Tor is ready 21.260
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.015
After features/support/hooks.rb:330 1.442
After features/support/hooks.rb:100 0.000