Project Number Date
test_Tails_ISO_devel 4353 21 Apr 2026, 07:40

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:41.894 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:11.223
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.051
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 13.434
When I start Tails from USB drive "old" with network unplugged 53.118
Then the boot device has safe access rights 2.779
And Tails is running from USB drive "old" 0.339
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.227
And I unplug USB drive "old" 0.124
After features/support/hooks.rb:331 1.291
After features/support/hooks.rb:100 0.007
Tags: @product
1:25.625
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login 54.551
Then Tails is running from USB drive "old" 0.322
And I create a persistent partition 25.280
And I take note of which tps features are available 0.729
Then a Tails persistence partition exists on USB drive "old" 0.560
And I shutdown Tails and wait for the computer to power off 4.133
After features/support/hooks.rb:331 0.316
After features/support/hooks.rb:100 0.007
Tags: @product
1:28.990
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.065
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.821
Then Tails is running from USB drive "old" 0.246
And all tps features are active 1.769
When I write some files expected to persist 1.405
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.196
And all persistence configuration files have safe access rights 0.452
And all persistent directories from the old Tails version have safe access rights 2.152
And I take note of which tps features are available 0.187
And I shutdown Tails and wait for the computer to power off 8.010
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.681
After features/support/hooks.rb:331 0.425
After features/support/hooks.rb:100 0.006
Tags: @product
2:12.735
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.072
And I log in to a new session 13.383
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.779
And I plug USB drive "to_upgrade" 2.243
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.806
Then the running Tails is installed on USB drive "to_upgrade" 16.182
And I unplug USB drive "to_upgrade" 0.127
And I unplug USB drive "__internal" 0.139
After features/support/hooks.rb:331 3.427
After features/support/hooks.rb:100 0.000
Tags: @product
1:10.734
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.049
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.854
Then all tps features from the old Tails version are active 1.006
And Tails is running from USB drive "to_upgrade" 0.276
And the boot device has safe access rights 2.640
And the expected persistent files created with the old Tails version are present in the filesystem 1.065
And all persistent directories from the old Tails version have safe access rights 1.841
After features/support/hooks.rb:331 0.958
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
4:44.032
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.408
And no SquashFS delta is installed 0.081
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.232
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.255
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.440
When the network is plugged 0.022
And Tor is ready 22.080
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.392
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.591
Given I shutdown Tails and wait for the computer to power off 19.128
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.651
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.137
And the file system changes introduced in version 6.2~testoverlayfs are present 0.227
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.148
# 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.015
And Tor is ready 21.580
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.370
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.783
Given I shutdown Tails and wait for the computer to power off 17.572
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.574
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.218
And the file system changes introduced in version 6.3~testoverlayfs are present 0.348
And only the 6.3~testoverlayfs SquashFS delta is installed 0.041
# 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.122
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.186
When the network is plugged 0.012
And Tor is ready 22.000
Then the Upgrader considers the system as up-to-date 0.108
# 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.549
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 0.949
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
28.552
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.482
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.225
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.049
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 19.355
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.372
After features/support/hooks.rb:331 0.920
After features/support/hooks.rb:100 0.000