Project Number Date
test_Tails_ISO_devel 4363 28 Apr 2026, 11:26

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 14:40.016 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:10.755
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.071
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 14.365
When I start Tails from USB drive "old" with network unplugged 51.712
Then the boot device has safe access rights 2.808
And Tails is running from USB drive "old" 0.281
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.049
And udev-watchdog is monitoring the correct device 0.249
And I unplug USB drive "old" 0.145
After features/support/hooks.rb:331 3.424
After features/support/hooks.rb:100 0.008
Tags: @product
1:25.195
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.071
And I start Tails from USB drive "old" with network unplugged and I login 54.799
Then Tails is running from USB drive "old" 0.260
And I create a persistent partition 24.424
And I take note of which tps features are available 0.690
Then a Tails persistence partition exists on USB drive "old" 0.577
And I shutdown Tails and wait for the computer to power off 4.372
After features/support/hooks.rb:331 0.209
After features/support/hooks.rb:100 0.007
Tags: @product
1:30.565
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.063
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.284
Then Tails is running from USB drive "old" 0.686
And all tps features are active 1.270
When I write some files expected to persist 1.414
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.200
And all persistence configuration files have safe access rights 0.450
And all persistent directories from the old Tails version have safe access rights 2.221
And I take note of which tps features are available 0.160
And I shutdown Tails and wait for the computer to power off 8.040
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.771
After features/support/hooks.rb:331 0.330
After features/support/hooks.rb:100 0.007
Tags: @product
2:17.406
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 7.837
And I log in to a new session 17.420
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.714
And I plug USB drive "to_upgrade" 2.231
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.361
Then the running Tails is installed on USB drive "to_upgrade" 16.517
And I unplug USB drive "to_upgrade" 0.153
And I unplug USB drive "__internal" 0.169
After features/support/hooks.rb:331 3.912
After features/support/hooks.rb:100 0.000
Tags: @product
1:12.104
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.074
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.597
Then all tps features from the old Tails version are active 1.005
And Tails is running from USB drive "to_upgrade" 0.313
And the boot device has safe access rights 2.761
And the expected persistent files created with the old Tails version are present in the filesystem 1.092
And all persistent directories from the old Tails version have safe access rights 2.259
After features/support/hooks.rb:331 0.700
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
6:36.124
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 8.597
And no SquashFS delta is installed 0.165
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.238
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.254
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.367
When the network is plugged 0.038
And Tor is ready 21.391
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.969
Given I shutdown Tails and wait for the computer to power off 14.308
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.561
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.073
And the file system changes introduced in version 6.2~testoverlayfs are present 0.207
And only the 6.2~testoverlayfs SquashFS delta is installed 0.043
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.146
# 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.195
When the network is plugged 0.016
And Tor is ready 13.533
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2:4.851
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.286
Given I shutdown Tails and wait for the computer to power off 17.454
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.896
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.102
And the file system changes introduced in version 6.3~testoverlayfs are present 0.373
And only the 6.3~testoverlayfs SquashFS delta is installed 0.057
# 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.117
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.191
When the network is plugged 0.018
And Tor is ready 21.064
Then the Upgrader considers the system as up-to-date 0.103
# 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.493
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.572
After features/support/hooks.rb:331 0.833
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
27.864
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 8.101
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.364
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.079
But a current signing key is available on our website 0.000
When the network is plugged 0.022
And Tor is ready 18.841
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.395
After features/support/hooks.rb:331 1.042
After features/support/hooks.rb:100 0.000