Project Number Date
test_Tails_ISO_devel 3896 04 Jul 2025, 13:06

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:54.767 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.266
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.275
And I create a 7200 MiB disk named "old" 0.054
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 28.918
When I start Tails from USB drive "old" with network unplugged 1:30.539
Then the boot device has safe access rights 3.426
And Tails is running from USB drive "old" 0.336
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.291
And I unplug USB drive "old" 0.200
After features/support/hooks.rb:330 7.161
After features/support/hooks.rb:100 0.009
Tags: @product
2:21.850
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login 1:35.696
Then Tails is running from USB drive "old" 0.431
And I create a persistent partition 33.366
And I take note of which tps features are available 2.623
Then a Tails persistence partition exists on USB drive "old" 0.821
And I shutdown Tails and wait for the computer to power off 8.719
After features/support/hooks.rb:330 0.207
After features/support/hooks.rb:100 0.009
Tags: @product
2:59.235
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.744
Then Tails is running from USB drive "old" 0.912
And all tps features are active 2.069
When I write some files expected to persist 1.821
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.194
And all persistence configuration files have safe access rights 0.361
And all persistent directories from the old Tails version have safe access rights 4.139
And I take note of which tps features are available 0.523
And I shutdown Tails and wait for the computer to power off 4.201
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.076
After features/support/hooks.rb:330 0.098
After features/support/hooks.rb:100 0.009
Tags: @product
2:38.247
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.518
And I log in to a new session 20.481
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.760
And I plug USB drive "to_upgrade" 2.388
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.069
Then the running Tails is installed on USB drive "to_upgrade" 27.630
And I unplug USB drive "to_upgrade" 0.184
And I unplug USB drive "__internal" 0.214
After features/support/hooks.rb:330 2.315
After features/support/hooks.rb:100 0.000
Tags: @product
2:35.914
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.256
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:25.856
Then all tps features from the old Tails version are active 1.910
And Tails is running from USB drive "to_upgrade" 0.351
And the boot device has safe access rights 3.480
And the expected persistent files created with the old Tails version are present in the filesystem 1.672
And all persistent directories from the old Tails version have safe access rights 2.387
After features/support/hooks.rb:330 1.734
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:14.114
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 11.093
And no SquashFS delta is installed 0.429
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.375
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.339
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.583
When the network is plugged 0.070
And Tor is ready 24.868
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.686
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.424
Given I shutdown Tails and wait for the computer to power off 8.911
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.425
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 2.124
And the file system changes introduced in version 6.2~testoverlayfs are present 0.307
And only the 6.2~testoverlayfs SquashFS delta is installed 0.082
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.346
# 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.338
When the network is plugged 0.065
And Tor is ready 19.818
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.528
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.459
Given I shutdown Tails and wait for the computer to power off 4.327
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.296
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.660
And the file system changes introduced in version 6.3~testoverlayfs are present 0.504
And only the 6.3~testoverlayfs SquashFS delta is installed 0.078
# 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.402
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.407
When the network is plugged 0.123
And Tor is ready 45.558
Then the Upgrader considers the system as up-to-date 0.345
# 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.496
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.533
After features/support/hooks.rb:330 1.097
After features/support/hooks.rb:100 0.070
Tags: @product @automatic_upgrade
1:0.138
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 9.610
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.388
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the signing key used by the Upgrader is outdated 0.163
But a current signing key is available on our website 0.000
When the network is plugged 0.105
And Tor is ready 49.122
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.676
After features/support/hooks.rb:330 0.770
After features/support/hooks.rb:100 0.000