Project Number Date
test_Tails_ISO_stable 6191 10 Mar 2026, 11:21

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:52.594 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:50.077
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.048
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.436
When I start Tails from USB drive "old" with network unplugged 1:31.996
Then the boot device has safe access rights 2.849
And Tails is running from USB drive "old" 0.251
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.064
And udev-watchdog is monitoring the correct device 0.175
And I unplug USB drive "old" 0.182
After features/support/hooks.rb:331 4.039
After features/support/hooks.rb:100 0.009
Tags: @product
1:30.329
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.118
And I start Tails from USB drive "old" with network unplugged and I login 55.832
Then Tails is running from USB drive "old" 0.267
And I create a persistent partition 24.566
And I take note of which tps features are available 0.726
Then a Tails persistence partition exists on USB drive "old" 0.522
And I shutdown Tails and wait for the computer to power off 8.295
After features/support/hooks.rb:331 0.581
After features/support/hooks.rb:100 0.007
Tags: @product
1:25.604
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.062
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.337
Then Tails is running from USB drive "old" 0.253
And all tps features are active 1.212
When I write some files expected to persist 1.315
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.182
And all persistence configuration files have safe access rights 0.466
And all persistent directories from the old Tails version have safe access rights 2.117
And I take note of which tps features are available 0.222
And I shutdown Tails and wait for the computer to power off 4.148
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.286
After features/support/hooks.rb:331 0.297
After features/support/hooks.rb:100 0.007
Tags: @product
2:17.802
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.839
And I log in to a new session 13.236
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.909
And I plug USB drive "to_upgrade" 2.321
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.669
Then the running Tails is installed on USB drive "to_upgrade" 16.511
And I unplug USB drive "to_upgrade" 0.167
And I unplug USB drive "__internal" 0.146
After features/support/hooks.rb:331 3.723
After features/support/hooks.rb:100 0.000
Tags: @product
1:12.432
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.087
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.226
Then all tps features from the old Tails version are active 0.971
And Tails is running from USB drive "to_upgrade" 0.299
And the boot device has safe access rights 2.830
And the expected persistent files created with the old Tails version are present in the filesystem 1.146
And all persistent directories from the old Tails version have safe access rights 1.871
After features/support/hooks.rb:331 0.879
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
5:6.010
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.535
And no SquashFS delta is installed 0.090
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.351
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
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.380
When the network is plugged 0.022
And Tor is ready 44.197
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.430
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.394
Given I shutdown Tails and wait for the computer to power off 19.742
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.699
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.102
And the file system changes introduced in version 6.2~testoverlayfs are present 0.239
And only the 6.2~testoverlayfs SquashFS delta is installed 0.048
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.141
# 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.197
When the network is plugged 0.017
And Tor is ready 20.341
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.373
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.079
Given I shutdown Tails and wait for the computer to power off 17.691
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.420
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.116
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.048
# 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.131
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.201
When the network is plugged 0.015
And Tor is ready 21.974
Then the Upgrader considers the system as up-to-date 0.117
# 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.767
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.427
After features/support/hooks.rb:331 1.129
After features/support/hooks.rb:100 0.063
Tags: @product @automatic_upgrade
30.337
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.330
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.060
And the signing key used by the Upgrader is outdated 0.048
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 21.224
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.368
After features/support/hooks.rb:331 0.946
After features/support/hooks.rb:100 0.000