Project Number Date
test_Tails_ISO_devel 4275 12 Mar 2026, 16: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 12:49.584 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:15.733
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.048
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 14.310
When I start Tails from USB drive "old" with network unplugged 56.620
Then the boot device has safe access rights 2.899
And Tails is running from USB drive "old" 0.293
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.080
And udev-watchdog is monitoring the correct device 0.244
And I unplug USB drive "old" 0.150
After features/support/hooks.rb:331 1.454
After features/support/hooks.rb:100 0.006
Tags: @product
1:30.762
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.056
And I start Tails from USB drive "old" with network unplugged and I login 55.568
Then Tails is running from USB drive "old" 0.241
And I create a persistent partition 25.274
And I take note of which tps features are available 0.845
Then a Tails persistence partition exists on USB drive "old" 0.617
And I shutdown Tails and wait for the computer to power off 8.158
After features/support/hooks.rb:331 0.164
After features/support/hooks.rb:100 0.007
Tags: @product
1:26.150
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.056
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.340
Then Tails is running from USB drive "old" 0.258
And all tps features are active 1.194
When I write some files expected to persist 1.353
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.210
And all persistence configuration files have safe access rights 0.562
And all persistent directories from the old Tails version have safe access rights 2.212
And I take note of which tps features are available 0.247
And I shutdown Tails and wait for the computer to power off 4.375
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.337
After features/support/hooks.rb:331 0.143
After features/support/hooks.rb:100 0.007
Tags: @product
2:23.066
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.661
And I log in to a new session 13.687
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.125
And I plug USB drive "to_upgrade" 2.281
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.707
Then the running Tails is installed on USB drive "to_upgrade" 16.307
And I unplug USB drive "to_upgrade" 0.138
And I unplug USB drive "__internal" 0.156
After features/support/hooks.rb:331 3.964
After features/support/hooks.rb:100 0.000
Tags: @product
1:10.638
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.063
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.267
Then all tps features from the old Tails version are active 1.037
And Tails is running from USB drive "to_upgrade" 0.261
And the boot device has safe access rights 2.598
And the expected persistent files created with the old Tails version are present in the filesystem 1.237
And all persistent directories from the old Tails version have safe access rights 2.172
After features/support/hooks.rb:331 0.664
After features/support/hooks.rb:100 0.034
Tags: @product @automatic_upgrade
4:35.980
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 8.511
And no SquashFS delta is installed 0.080
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.214
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.238
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.423
When the network is plugged 0.016
And Tor is ready 24.006
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.368
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.019
Given I shutdown Tails and wait for the computer to power off 11.451
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.678
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 1.335
And the file system changes introduced in version 6.2~testoverlayfs are present 0.260
And only the 6.2~testoverlayfs SquashFS delta is installed 0.042
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.126
# 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.206
When the network is plugged 0.022
And Tor is ready 21.555
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.360
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.186
Given I shutdown Tails and wait for the computer to power off 17.717
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.916
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.315
And the file system changes introduced in version 6.3~testoverlayfs are present 0.443
And only the 6.3~testoverlayfs SquashFS delta is installed 0.058
# 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.194
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.193
When the network is plugged 0.015
And Tor is ready 21.101
Then the Upgrader considers the system as up-to-date 0.127
# 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.374
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.341
After features/support/hooks.rb:331 0.671
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
27.252
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.539
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.267
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 18.878
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.444
After features/support/hooks.rb:331 1.069
After features/support/hooks.rb:100 0.000