Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 1 20 Apr 2026, 19:31

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 13:30.511 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
1:18.555
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.085
And I create a 7200 MiB disk named "old" 0.016
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 14.672
When I start Tails from USB drive "old" with network unplugged 58.629
Then the boot device has safe access rights 3.304
And Tails is running from USB drive "old" 0.282
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.071
And udev-watchdog is monitoring the correct device 0.278
And I unplug USB drive "old" 0.147
After features/support/hooks.rb:331 1.429
After features/support/hooks.rb:100 0.010
Tags: @product
1:32.278
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.069
And I start Tails from USB drive "old" with network unplugged and I login 59.992
Then Tails is running from USB drive "old" 0.249
And I create a persistent partition 25.909
And I take note of which tps features are available 0.974
Then a Tails persistence partition exists on USB drive "old" 0.636
And I shutdown Tails and wait for the computer to power off 4.447
After features/support/hooks.rb:331 0.633
After features/support/hooks.rb:100 0.009
Tags: @product
1:33.189
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:8.158
Then Tails is running from USB drive "old" 0.327
And all tps features are active 1.299
When I write some files expected to persist 1.614
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.216
And all persistence configuration files have safe access rights 0.642
And all persistent directories from the old Tails version have safe access rights 2.325
And I take note of which tps features are available 0.170
And I shutdown Tails and wait for the computer to power off 4.733
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.625
After features/support/hooks.rb:331 0.210
After features/support/hooks.rb:100 0.009
Tags: @product
2:19.159
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 8.740
And I log in to a new session 13.190
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.612
And I plug USB drive "to_upgrade" 2.325
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.610
Then the running Tails is installed on USB drive "to_upgrade" 19.370
And I unplug USB drive "to_upgrade" 0.163
And I unplug USB drive "__internal" 0.145
After features/support/hooks.rb:331 2.220
After features/support/hooks.rb:100 0.000
Tags: @product
1:18.246
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.069
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:10.258
Then all tps features from the old Tails version are active 1.438
And Tails is running from USB drive "to_upgrade" 0.259
And the boot device has safe access rights 2.600
And the expected persistent files created with the old Tails version are present in the filesystem 1.418
And all persistent directories from the old Tails version have safe access rights 2.202
After features/support/hooks.rb:331 1.025
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
4:59.016
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.229
And no SquashFS delta is installed 0.115
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.284
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.224
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.381
When the network is plugged 0.016
And Tor is ready 23.457
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.425
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.966
Given I shutdown Tails and wait for the computer to power off 19.885
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:20.541
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.524
And the file system changes introduced in version 6.2~testoverlayfs are present 0.394
And only the 6.2~testoverlayfs SquashFS delta is installed 0.052
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.167
# 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.210
When the network is plugged 0.014
And Tor is ready 22.085
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.505
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.577
Given I shutdown Tails and wait for the computer to power off 17.284
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:20.337
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 1.424
And the file system changes introduced in version 6.3~testoverlayfs are present 0.481
And only the 6.3~testoverlayfs SquashFS delta is installed 0.050
# 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.184
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.244
When the network is plugged 0.021
And Tor is ready 21.733
Then the Upgrader considers the system as up-to-date 0.142
# 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 4.483
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.504
After features/support/hooks.rb:331 1.066
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
30.065
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 9.055
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.328
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the signing key used by the Upgrader is outdated 0.047
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 20.132
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.441
After features/support/hooks.rb:331 0.927
After features/support/hooks.rb:100 0.000