Project Number Date
test_Tails_ISO_devel 4661 07 Oct 2026, 08:07

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:32.081 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:23.374
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.108
And I create a 7200 MiB disk named "old" 0.025
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.590
When I start Tails from USB drive "old" with network unplugged 1:5.359
Then the boot device has safe access rights 2.543
And Tails is running from USB drive "old" 0.277
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.203
And I unplug USB drive "old" 0.118
After features/support/hooks.rb:339 4.104
After features/support/hooks.rb:108 0.007
Tags: @product
1:35.896
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.090
And I start Tails from USB drive "old" with network unplugged and I login 52.616
Then Tails is running from USB drive "old" 0.233
And I create a persistent partition 29.122
And I take note of which tps features are available 8.882
Then a Tails persistence partition exists on USB drive "old" 0.610
And I shutdown Tails and wait for the computer to power off 4.340
After features/support/hooks.rb:339 0.551
After features/support/hooks.rb:108 0.013
Tags: @product
1:46.770
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.007
Given a computer 1.923
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:10.008
Then Tails is running from USB drive "old" 0.279
And all tps features are active 8.412
When I write some files expected to persist 1.251
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.181
And all persistence configuration files have safe access rights 0.327
And all persistent directories from the old Tails version have safe access rights 1.773
And I take note of which tps features are available 6.468
And I shutdown Tails and wait for the computer to power off 4.097
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 12.046
After features/support/hooks.rb:339 0.584
After features/support/hooks.rb:108 0.006
Tags: @product
2:15.748
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.982
And I log in to a new session 12.067
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.904
And I plug USB drive "to_upgrade" 2.203
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.267
Then the running Tails is installed on USB drive "to_upgrade" 20.076
And I unplug USB drive "to_upgrade" 0.114
And I unplug USB drive "__internal" 0.131
After features/support/hooks.rb:339 2.272
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.479
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.100
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.244
Then all tps features from the old Tails version are active 1.025
And Tails is running from USB drive "to_upgrade" 0.239
And the boot device has safe access rights 2.267
And the expected persistent files created with the old Tails version are present in the filesystem 0.918
And all persistent directories from the old Tails version have safe access rights 1.682
After features/support/hooks.rb:339 0.706
After features/support/hooks.rb:108 0.015
Tags: @product @automatic_upgrade
3:45.296
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.486
And no SquashFS delta is installed 0.081
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.349
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.086
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.289
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.383
When the network is plugged 0.038
And Tor is ready 11.609
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.659
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.676
Given I shutdown Tails and wait for the computer to power off 5.418
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.700
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.354
And the file system changes introduced in version 6.2~testoverlayfs are present 0.224
And only the 6.2~testoverlayfs SquashFS delta is installed 0.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.131
# 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.169
When the network is plugged 0.030
And Tor is ready 10.606
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.333
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.626
Given I shutdown Tails and wait for the computer to power off 4.133
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.570
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 10.121
And the file system changes introduced in version 6.3~testoverlayfs are present 0.364
And only the 6.3~testoverlayfs SquashFS delta is installed 0.055
# 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.140
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.187
When the network is plugged 0.040
And Tor is ready 10.264
Then the Upgrader considers the system as up-to-date 0.080
# 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 3.669
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.335
After features/support/hooks.rb:339 0.619
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
33.515
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 22.184
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.196
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the signing key used by the Upgrader is outdated 0.065
But a current signing key is available on our website 0.000
When the network is plugged 0.032
And Tor is ready 9.425
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.567
After features/support/hooks.rb:339 0.667
After features/support/hooks.rb:108 0.000