Project Number Date
test_Tails_ISO_stable 5677 26 May 2025, 12:37

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:13.212 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:12.292
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.193
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 31.066
When I start Tails from USB drive "old" with network unplugged 1:35.778
Then the boot device has safe access rights 3.174
And Tails is running from USB drive "old" 0.342
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.087
And udev-watchdog is monitoring the correct device 0.298
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:330 6.730
After features/support/hooks.rb:100 0.040
Tags: @product
2:8.134
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login 1:24.507
Then Tails is running from USB drive "old" 0.338
And I create a persistent partition 32.304
And I take note of which tps features are available 1.843
Then a Tails persistence partition exists on USB drive "old" 0.756
And I shutdown Tails and wait for the computer to power off 8.203
After features/support/hooks.rb:330 0.179
After features/support/hooks.rb:100 0.007
Tags: @product
2:58.988
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.169
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.540
Then Tails is running from USB drive "old" 0.338
And all tps features are active 1.764
When I write some files expected to persist 1.800
# 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.391
And all persistent directories from the old Tails version have safe access rights 2.763
And I take note of which tps features are available 0.385
And I shutdown Tails and wait for the computer to power off 4.276
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.317
After features/support/hooks.rb:330 0.152
After features/support/hooks.rb:100 0.009
Tags: @product
2:32.338
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.588
And I log in to a new session 18.164
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.950
And I plug USB drive "to_upgrade" 2.471
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.125
Then the running Tails is installed on USB drive "to_upgrade" 24.625
And I unplug USB drive "to_upgrade" 0.209
And I unplug USB drive "__internal" 0.201
After features/support/hooks.rb:330 6.938
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.875
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.170
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.438
Then all tps features from the old Tails version are active 1.616
And Tails is running from USB drive "to_upgrade" 0.336
And the boot device has safe access rights 3.348
And the expected persistent files created with the old Tails version are present in the filesystem 1.403
And all persistent directories from the old Tails version have safe access rights 2.561
After features/support/hooks.rb:330 1.769
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:21.186
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.541
And no SquashFS delta is installed 0.058
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.527
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.469
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.406
When the network is plugged 0.069
And Tor is ready 21.168
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.980
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.019
Given I shutdown Tails and wait for the computer to power off 8.611
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.832
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.372
And the file system changes introduced in version 6.2~testoverlayfs are present 0.432
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.312
# 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.306
When the network is plugged 0.060
And Tor is ready 18.052
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.548
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.913
Given I shutdown Tails and wait for the computer to power off 4.316
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.712
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 1.884
And the file system changes introduced in version 6.3~testoverlayfs are present 0.442
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.325
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.366
When the network is plugged 0.066
And Tor is ready 17.545
Then the Upgrader considers the system as up-to-date 0.302
# 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.777
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.508
After features/support/hooks.rb:330 0.734
After features/support/hooks.rb:100 0.048
Tags: @product @automatic_upgrade
39.395
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.384
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.428
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.096
And the signing key used by the Upgrader is outdated 0.121
But a current signing key is available on our website 0.000
When the network is plugged 0.067
And Tor is ready 20.418
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.879
After features/support/hooks.rb:330 1.038
After features/support/hooks.rb:100 0.000