Project Number Date
test_Tails_ISO_devel 3826 21 May 2025, 09:42

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:23.994 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:18.556
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.013
Given a computer 0.263
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 31.633
When I start Tails from USB drive "old" with network unplugged 1:41.042
Then the boot device has safe access rights 3.412
And Tails is running from USB drive "old" 0.351
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.124
And udev-watchdog is monitoring the correct device 0.364
And I unplug USB drive "old" 0.179
After features/support/hooks.rb:330 3.734
After features/support/hooks.rb:100 0.012
Tags: @product
2:26.407
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given a computer 0.193
And I start Tails from USB drive "old" with network unplugged and I login 1:42.069
Then Tails is running from USB drive "old" 0.313
And I create a persistent partition 32.837
And I take note of which tps features are available 2.016
Then a Tails persistence partition exists on USB drive "old" 0.735
And I shutdown Tails and wait for the computer to power off 8.242
After features/support/hooks.rb:330 0.178
After features/support/hooks.rb:100 0.009
Tags: @product
3:6.623
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:27.599
Then Tails is running from USB drive "old" 0.988
And all tps features are active 1.980
When I write some files expected to persist 1.648
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.236
And all persistence configuration files have safe access rights 0.387
And all persistent directories from the old Tails version have safe access rights 2.717
And I take note of which tps features are available 0.420
And I shutdown Tails and wait for the computer to power off 6.219
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.228
After features/support/hooks.rb:330 0.106
After features/support/hooks.rb:100 0.009
Tags: @product
2:36.082
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 without a persistent partition and stopped at Tails Greeter's login screen 11.338
And I log in to a new session 20.224
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.637
And I plug USB drive "to_upgrade" 2.425
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.844
Then the running Tails is installed on USB drive "to_upgrade" 25.144
And I unplug USB drive "to_upgrade" 0.239
And I unplug USB drive "__internal" 0.227
After features/support/hooks.rb:330 1.963
After features/support/hooks.rb:100 0.000
Tags: @product
2:27.472
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.213
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:17.823
Then all tps features from the old Tails version are active 1.772
And Tails is running from USB drive "to_upgrade" 0.375
And the boot device has safe access rights 3.460
And the expected persistent files created with the old Tails version are present in the filesystem 1.435
And all persistent directories from the old Tails version have safe access rights 2.392
After features/support/hooks.rb:330 1.646
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:50.545
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 14.488
And no SquashFS delta is installed 0.262
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.370
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.297
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.474
When the network is plugged 0.090
And Tor is ready 19.824
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.631
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.514
Given I shutdown Tails and wait for the computer to power off 8.898
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.535
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.185
And the file system changes introduced in version 6.2~testoverlayfs are present 0.270
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.289
# 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.275
When the network is plugged 0.094
And Tor is ready 19.925
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.836
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.327
Given I shutdown Tails and wait for the computer to power off 4.252
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.688
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.866
And the file system changes introduced in version 6.3~testoverlayfs are present 0.548
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.480
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.300
When the network is plugged 0.068
And Tor is ready 20.207
Then the Upgrader considers the system as up-to-date 10.837
# 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.923
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.540
After features/support/hooks.rb:330 0.722
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
38.306
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 10.593
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.429
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.101
And the signing key used by the Upgrader is outdated 0.070
But a current signing key is available on our website 0.000
When the network is plugged 0.088
And Tor is ready 17.402
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.620
After features/support/hooks.rb:330 0.893
After features/support/hooks.rb:100 0.000