Project Number Date
test_Tails_ISO_stable 6050 10 Jan 2026, 11:39

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 11:36.260 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:7.708
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.054
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.925
When I start Tails from USB drive "old" with network unplugged 49.070
Then the boot device has safe access rights 2.822
And Tails is running from USB drive "old" 0.247
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.064
And udev-watchdog is monitoring the correct device 0.298
And I unplug USB drive "old" 0.137
After features/support/hooks.rb:331 3.394
After features/support/hooks.rb:100 0.012
Tags: @product
1:30.337
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.076
And I start Tails from USB drive "old" with network unplugged and I login 54.740
Then Tails is running from USB drive "old" 0.265
And I create a persistent partition 25.554
And I take note of which tps features are available 0.748
Then a Tails persistence partition exists on USB drive "old" 0.600
And I shutdown Tails and wait for the computer to power off 8.351
After features/support/hooks.rb:331 0.543
After features/support/hooks.rb:100 0.006
Tags: @product
1:26.234
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.550
Then Tails is running from USB drive "old" 0.223
And all tps features are active 1.098
When I write some files expected to persist 1.457
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.171
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.846
And I take note of which tps features are available 0.133
And I shutdown Tails and wait for the computer to power off 8.406
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.969
After features/support/hooks.rb:331 0.676
After features/support/hooks.rb:100 0.006
Tags: @product
2:15.411
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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.931
And I log in to a new session 14.325
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.873
And I plug USB drive "to_upgrade" 2.205
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.473
Then the running Tails is installed on USB drive "to_upgrade" 16.313
And I unplug USB drive "to_upgrade" 0.146
And I unplug USB drive "__internal" 0.143
After features/support/hooks.rb:331 3.718
After features/support/hooks.rb:100 0.000
Tags: @product
1:11.464
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
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.796
Then all tps features from the old Tails version are active 1.131
And Tails is running from USB drive "to_upgrade" 0.304
And the boot device has safe access rights 2.849
And the expected persistent files created with the old Tails version are present in the filesystem 1.139
And all persistent directories from the old Tails version have safe access rights 2.179
After features/support/hooks.rb:331 0.811
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
3:44.783
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.230
And no SquashFS delta is installed 0.111
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.392
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.294
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.418
When the network is plugged 0.018
And Tor is ready 13.655
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.996
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.361
Given I shutdown Tails and wait for the computer to power off 9.828
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.498
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.297
And the file system changes introduced in version 6.2~testoverlayfs are present 0.243
And only the 6.2~testoverlayfs SquashFS delta is installed 0.047
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.134
# 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.268
When the network is plugged 0.015
And Tor is ready 11.735
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.823
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.190
Given I shutdown Tails and wait for the computer to power off 8.200
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.932
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.452
And the file system changes introduced in version 6.3~testoverlayfs are present 0.401
And only the 6.3~testoverlayfs SquashFS delta is installed 0.042
# 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.153
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.276
When the network is plugged 0.022
And Tor is ready 11.373
Then the Upgrader considers the system as up-to-date 10.548
# 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.281
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.469
After features/support/hooks.rb:331 0.748
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
20.319
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.830
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.274
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
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.017
And Tor is ready 10.134
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.944
After features/support/hooks.rb:331 0.973
After features/support/hooks.rb:100 0.000