Project Number Date
test_Tails_ISO_stable 5743 27 Jun 2025, 00:05

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 21:46.720 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:17.568
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.061
Given a computer 0.605
And I create a 7200 MiB disk named "old" 0.084
And I plug USB drive "old" 1.105
And I write an old version of the Tails USB image to disk "old" 32.237
When I start Tails from USB drive "old" with network unplugged 1:39.005
Then the boot device has safe access rights 3.324
And Tails is running from USB drive "old" 0.348
And there is no persistence partition on USB drive "old" 0.098
And process "udev-watchdog" is running 0.131
And udev-watchdog is monitoring the correct device 0.439
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:330 0.879
After features/support/hooks.rb:100 0.054
Tags: @product
2:26.416
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.031
Given a computer 0.832
And I start Tails from USB drive "old" with network unplugged and I login 1:36.619
Then Tails is running from USB drive "old" 0.513
And I create a persistent partition 36.560
And I take note of which tps features are available 2.483
Then a Tails persistence partition exists on USB drive "old" 0.834
And I shutdown Tails and wait for the computer to power off 8.571
After features/support/hooks.rb:330 0.416
After features/support/hooks.rb:100 0.047
Tags: @product
3:21.075
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.228
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:33.697
Then Tails is running from USB drive "old" 0.798
And all tps features are active 3.109
When I write some files expected to persist 4.169
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.306
And all persistence configuration files have safe access rights 0.413
And all persistent directories from the old Tails version have safe access rights 2.751
And I take note of which tps features are available 0.436
And I shutdown Tails and wait for the computer to power off 4.506
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 30.657
After features/support/hooks.rb:330 0.129
After features/support/hooks.rb:100 0.009
Tags: @product
2:44.452
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 10.341
And I log in to a new session 24.190
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.138
And I plug USB drive "to_upgrade" 2.663
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.290
Then the running Tails is installed on USB drive "to_upgrade" 26.403
And I unplug USB drive "to_upgrade" 0.198
And I unplug USB drive "__internal" 0.226
After features/support/hooks.rb:330 0.962
After features/support/hooks.rb:100 0.000
Tags: @product
2:32.290
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.203
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:19.643
Then all tps features from the old Tails version are active 1.640
And Tails is running from USB drive "to_upgrade" 0.338
And the boot device has safe access rights 3.813
And the expected persistent files created with the old Tails version are present in the filesystem 3.004
And all persistent directories from the old Tails version have safe access rights 3.645
After features/support/hooks.rb:330 1.800
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:46.048
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.473
And no SquashFS delta is installed 0.085
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.432
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.085
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.638
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.930
When the network is plugged 0.190
And Tor is ready 25.125
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.014
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.353
Given I shutdown Tails and wait for the computer to power off 9.377
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:18.514
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.540
And the file system changes introduced in version 6.2~testoverlayfs are present 0.906
And only the 6.2~testoverlayfs SquashFS delta is installed 0.632
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.499
# 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.513
When the network is plugged 0.084
And Tor is ready 17.426
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.213
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.596
Given I shutdown Tails and wait for the computer to power off 7.231
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.831
Then Tails is running version 6.3~testoverlayfs 0.152
And all tps features are active 3.665
And the file system changes introduced in version 6.3~testoverlayfs are present 0.866
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.290
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.445
When the network is plugged 0.082
And Tor is ready 48.273
Then the Upgrader considers the system as up-to-date 0.311
# 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 17.381
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.792
After features/support/hooks.rb:330 0.903
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
38.870
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.246
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.577
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.170
And the signing key used by the Upgrader is outdated 0.139
But a current signing key is available on our website 0.000
When the network is plugged 0.066
And Tor is ready 17.677
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.990
After features/support/hooks.rb:330 0.877
After features/support/hooks.rb:100 0.000