Project Number Date
test_Tails_ISO_stable 5591 23 Apr 2025, 21:11

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:7.382 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:5.881
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.188
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.060
And I write an old version of the Tails USB image to disk "old" 31.262
When I start Tails from USB drive "old" with network unplugged 1:29.072
Then the boot device has safe access rights 3.204
And Tails is running from USB drive "old" 0.346
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.108
And udev-watchdog is monitoring the correct device 0.318
And I unplug USB drive "old" 0.194
After features/support/hooks.rb:330 7.021
After features/support/hooks.rb:100 0.008
Tags: @product
2:15.033
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login 1:33.504
Then Tails is running from USB drive "old" 0.324
And I create a persistent partition 31.891
And I take note of which tps features are available 1.890
Then a Tails persistence partition exists on USB drive "old" 0.774
And I shutdown Tails and wait for the computer to power off 6.447
After features/support/hooks.rb:330 0.150
After features/support/hooks.rb:100 0.009
Tags: @product
2:52.167
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.213
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.402
Then Tails is running from USB drive "old" 0.456
And all tps features are active 2.156
When I write some files expected to persist 2.038
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.340
And all persistence configuration files have safe access rights 0.588
And all persistent directories from the old Tails version have safe access rights 2.928
And I take note of which tps features are available 0.476
And I shutdown Tails and wait for the computer to power off 6.410
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.157
After features/support/hooks.rb:330 0.112
After features/support/hooks.rb:100 0.008
Tags: @product
2:33.869
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 without a persistent partition and stopped at Tails Greeter's login screen 10.801
And I log in to a new session 19.395
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.998
And I plug USB drive "to_upgrade" 2.588
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.173
Then the running Tails is installed on USB drive "to_upgrade" 24.463
And I unplug USB drive "to_upgrade" 0.217
And I unplug USB drive "__internal" 0.230
After features/support/hooks.rb:330 0.988
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.249
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.181
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.656
Then all tps features from the old Tails version are active 1.669
And Tails is running from USB drive "to_upgrade" 0.320
And the boot device has safe access rights 3.456
And the expected persistent files created with the old Tails version are present in the filesystem 1.477
And all persistent directories from the old Tails version have safe access rights 2.488
After features/support/hooks.rb:330 0.805
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:13.906
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.050
And no SquashFS delta is installed 0.178
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.415
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.374
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.483
When the network is plugged 0.059
And Tor is ready 21.656
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.040
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.961
Given I shutdown Tails and wait for the computer to power off 8.858
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:20.588
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.106
And the file system changes introduced in version 6.2~testoverlayfs are present 0.317
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.299
# 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.295
When the network is plugged 0.061
And Tor is ready 46.254
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.630
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.214
Given I shutdown Tails and wait for the computer to power off 4.789
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.816
Then Tails is running version 6.3~testoverlayfs 0.020
And all tps features are active 1.917
And the file system changes introduced in version 6.3~testoverlayfs are present 0.544
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.298
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.269
When the network is plugged 0.072
And Tor is ready 16.929
Then the Upgrader considers the system as up-to-date 0.346
# 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.316
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.515
After features/support/hooks.rb:330 0.747
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
42.274
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 10.303
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.425
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.099
And the signing key used by the Upgrader is outdated 0.075
But a current signing key is available on our website 0.000
When the network is plugged 0.068
And Tor is ready 30.663
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.638
After features/support/hooks.rb:330 0.858
After features/support/hooks.rb:100 0.000