Project Number Date
test_Tails_ISO_devel 4289 23 Mar 2026, 11: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 13:20.013 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:14.024
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.098
And I create a 7200 MiB disk named "old" 0.028
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 14.395
When I start Tails from USB drive "old" with network unplugged 54.260
Then the boot device has safe access rights 3.316
And Tails is running from USB drive "old" 0.361
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.234
And I unplug USB drive "old" 0.152
After features/support/hooks.rb:331 1.491
After features/support/hooks.rb:100 0.008
Tags: @product
1:31.854
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.072
And I start Tails from USB drive "old" with network unplugged and I login 57.080
Then Tails is running from USB drive "old" 0.293
And I create a persistent partition 24.723
And I take note of which tps features are available 0.925
Then a Tails persistence partition exists on USB drive "old" 0.673
And I shutdown Tails and wait for the computer to power off 8.086
After features/support/hooks.rb:331 0.610
After features/support/hooks.rb:100 0.007
Tags: @product
1:32.566
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.066
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.172
Then Tails is running from USB drive "old" 0.272
And all tps features are active 1.504
When I write some files expected to persist 1.460
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.217
And all persistence configuration files have safe access rights 0.691
And all persistent directories from the old Tails version have safe access rights 2.208
And I take note of which tps features are available 0.259
And I shutdown Tails and wait for the computer to power off 7.974
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.738
After features/support/hooks.rb:331 0.265
After features/support/hooks.rb:100 0.006
Tags: @product
2:14.625
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.441
And I log in to a new session 13.585
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.925
And I plug USB drive "to_upgrade" 2.234
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.472
Then the running Tails is installed on USB drive "to_upgrade" 16.663
And I unplug USB drive "to_upgrade" 0.141
And I unplug USB drive "__internal" 0.160
After features/support/hooks.rb:331 2.394
After features/support/hooks.rb:100 0.000
Tags: @product
1:15.173
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.116
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.199
Then all tps features from the old Tails version are active 1.070
And Tails is running from USB drive "to_upgrade" 0.231
And the boot device has safe access rights 2.805
And the expected persistent files created with the old Tails version are present in the filesystem 1.209
And all persistent directories from the old Tails version have safe access rights 2.539
After features/support/hooks.rb:331 0.663
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
5:3.990
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 21.945
And no SquashFS delta is installed 0.100
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.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.268
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.383
When the network is plugged 0.028
And Tor is ready 22.011
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.479
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.959
Given I shutdown Tails and wait for the computer to power off 15.046
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.403
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.419
And the file system changes introduced in version 6.2~testoverlayfs are present 0.346
And only the 6.2~testoverlayfs SquashFS delta is installed 0.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.213
# 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.254
When the network is plugged 0.016
And Tor is ready 40.056
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.457
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.548
Given I shutdown Tails and wait for the computer to power off 4.166
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.251
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.224
And the file system changes introduced in version 6.3~testoverlayfs are present 0.384
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.148
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.296
When the network is plugged 0.017
And Tor is ready 21.743
Then the Upgrader considers the system as up-to-date 0.111
# 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.812
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.439
After features/support/hooks.rb:331 1.041
After features/support/hooks.rb:100 0.037
Tags: @product @automatic_upgrade
27.778
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.546
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.207
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.050
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 18.456
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.438
After features/support/hooks.rb:331 1.240
After features/support/hooks.rb:100 0.000