Project Number Date
test_Tails_ISO_devel 4315 03 Apr 2026, 07:36

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:4.416 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:12.829
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.060
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 13.125
When I start Tails from USB drive "old" with network unplugged 55.301
Then the boot device has safe access rights 2.617
And Tails is running from USB drive "old" 0.267
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.177
And I unplug USB drive "old" 0.149
After features/support/hooks.rb:331 1.158
After features/support/hooks.rb:100 0.006
Tags: @product
1:22.882
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.055
And I start Tails from USB drive "old" with network unplugged and I login 52.976
Then Tails is running from USB drive "old" 0.267
And I create a persistent partition 24.160
And I take note of which tps features are available 0.665
Then a Tails persistence partition exists on USB drive "old" 0.554
And I shutdown Tails and wait for the computer to power off 4.203
After features/support/hooks.rb:331 0.437
After features/support/hooks.rb:100 0.005
Tags: @product
1:23.199
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.046
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.242
Then Tails is running from USB drive "old" 0.239
And all tps features are active 1.188
When I write some files expected to persist 1.254
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.193
And all persistence configuration files have safe access rights 0.397
And all persistent directories from the old Tails version have safe access rights 1.814
And I take note of which tps features are available 0.158
And I shutdown Tails and wait for the computer to power off 7.891
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.772
After features/support/hooks.rb:331 0.158
After features/support/hooks.rb:100 0.006
Tags: @product
2:9.200
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.168
And I log in to a new session 11.440
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.764
And I plug USB drive "to_upgrade" 2.246
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.393
Then the running Tails is installed on USB drive "to_upgrade" 14.916
And I unplug USB drive "to_upgrade" 0.125
And I unplug USB drive "__internal" 0.144
After features/support/hooks.rb:331 0.609
After features/support/hooks.rb:100 0.000
Tags: @product
1:6.167
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.048
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.492
Then all tps features from the old Tails version are active 0.933
And Tails is running from USB drive "to_upgrade" 0.272
And the boot device has safe access rights 2.416
And the expected persistent files created with the old Tails version are present in the filesystem 1.091
And all persistent directories from the old Tails version have safe access rights 1.911
After features/support/hooks.rb:331 0.758
After features/support/hooks.rb:100 0.006
4:26.553
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 with a persistent partition enabled and logged in 7.966
And no SquashFS delta is installed 0.062
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.198
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.227
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.348
When the network is plugged 0.018
And Tor is ready 19.780
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.343
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.967
Given I shutdown Tails and wait for the computer to power off 19.939
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.832
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.094
And the file system changes introduced in version 6.2~testoverlayfs are present 0.250
And only the 6.2~testoverlayfs SquashFS delta is installed 0.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.133
# 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.208
When the network is plugged 0.014
And Tor is ready 21.190
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.363
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.580
Given I shutdown Tails and wait for the computer to power off 17.084
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.220
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 1.048
And the file system changes introduced in version 6.3~testoverlayfs are present 0.346
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.165
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.220
When the network is plugged 0.021
And Tor is ready 20.185
Then the Upgrader considers the system as up-to-date 0.093
# 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.122
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.357
After features/support/hooks.rb:331 0.887
After features/support/hooks.rb:100 0.035
23.583
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 with a persistent partition enabled and logged in 7.365
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.235
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.031
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.013
And Tor is ready 15.534
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.358
After features/support/hooks.rb:331 0.786
After features/support/hooks.rb:100 0.000