Project Number Date
test_Tails_ISO_devel 3881 23 Jun 2025, 13:17

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 24:5.497 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:13.673
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.021
Given a computer 0.268
And I create a 7200 MiB disk named "old" 0.038
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 37.565
When I start Tails from USB drive "old" with network unplugged 1:29.672
Then the boot device has safe access rights 3.846
And Tails is running from USB drive "old" 0.375
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.140
And udev-watchdog is monitoring the correct device 0.376
And I unplug USB drive "old" 0.262
After features/support/hooks.rb:330 3.768
After features/support/hooks.rb:100 0.011
Tags: @product
2:15.585
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.211
And I start Tails from USB drive "old" with network unplugged and I login 1:29.411
Then Tails is running from USB drive "old" 0.386
And I create a persistent partition 33.058
And I take note of which tps features are available 2.776
Then a Tails persistence partition exists on USB drive "old" 0.747
And I shutdown Tails and wait for the computer to power off 8.992
After features/support/hooks.rb:330 0.320
After features/support/hooks.rb:100 0.009
Tags: @product
3:16.706
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.193
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:36.648
Then Tails is running from USB drive "old" 0.939
And all tps features are active 2.371
When I write some files expected to persist 2.217
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.238
And all persistence configuration files have safe access rights 0.419
And all persistent directories from the old Tails version have safe access rights 2.598
And I take note of which tps features are available 0.520
And I shutdown Tails and wait for the computer to power off 4.355
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.203
After features/support/hooks.rb:330 0.392
After features/support/hooks.rb:100 0.020
Tags: @product
2:47.280
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 15.572
And I log in to a new session 21.008
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.282
And I plug USB drive "to_upgrade" 2.548
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.737
Then the running Tails is installed on USB drive "to_upgrade" 28.696
And I unplug USB drive "to_upgrade" 0.190
And I unplug USB drive "__internal" 0.242
After features/support/hooks.rb:330 2.503
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.801
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.186
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.093
Then all tps features from the old Tails version are active 1.967
And Tails is running from USB drive "to_upgrade" 0.509
And the boot device has safe access rights 3.811
And the expected persistent files created with the old Tails version are present in the filesystem 1.656
And all persistent directories from the old Tails version have safe access rights 2.577
After features/support/hooks.rb:330 1.092
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
10:32.623
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 13.853
And no SquashFS delta is installed 0.082
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.363
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.502
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.586
When the network is plugged 0.058
And Tor is ready 17.879
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.823
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.463
Given I shutdown Tails and wait for the computer to power off 1:20.216
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.522
Then Tails is running version 6.2~testoverlayfs 0.034
And all tps features are active 2.411
And the file system changes introduced in version 6.2~testoverlayfs are present 0.418
And only the 6.2~testoverlayfs SquashFS delta is installed 0.086
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.486
# 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.790
When the network is plugged 0.125
And Tor is ready 46.055
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.577
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 2:14.255
Given I shutdown Tails and wait for the computer to power off 7.100
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.413
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.198
And the file system changes introduced in version 6.3~testoverlayfs are present 0.458
And only the 6.3~testoverlayfs SquashFS delta is installed 0.117
# 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.370
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.245
When the network is plugged 0.070
And Tor is ready 18.309
Then the Upgrader considers the system as up-to-date 0.381
# 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.558
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.720
After features/support/hooks.rb:330 0.979
After features/support/hooks.rb:100 0.046
Tags: @product @automatic_upgrade
37.826
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.443
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.331
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.156
And the signing key used by the Upgrader is outdated 0.107
But a current signing key is available on our website 0.000
When the network is plugged 0.136
And Tor is ready 19.977
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.673
After features/support/hooks.rb:330 1.115
After features/support/hooks.rb:100 0.000