Project Number Date
test_Tails_ISO_devel 4036 25 Oct 2025, 11:58

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 14:54.825 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:37.564
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.326
And I create a 7200 MiB disk named "old" 0.064
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 24.724
When I start Tails from USB drive "old" with network unplugged 1:7.739
Then the boot device has safe access rights 2.829
And Tails is running from USB drive "old" 0.298
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.222
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:331 3.732
After features/support/hooks.rb:100 0.033
Tags: @product
2:0.865
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login 1:21.821
Then Tails is running from USB drive "old" 0.329
And I create a persistent partition 28.861
And I take note of which tps features are available 1.213
Then a Tails persistence partition exists on USB drive "old" 0.635
And I shutdown Tails and wait for the computer to power off 7.799
After features/support/hooks.rb:331 0.567
After features/support/hooks.rb:100 0.007
Tags: @product
2:5.945
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.223
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:32.971
Then Tails is running from USB drive "old" 0.275
And all tps features are active 1.977
When I write some files expected to persist 1.512
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.233
And all persistence configuration files have safe access rights 0.435
And all persistent directories from the old Tails version have safe access rights 2.322
And I take note of which tps features are available 0.625
And I shutdown Tails and wait for the computer to power off 7.579
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.787
After features/support/hooks.rb:331 0.556
After features/support/hooks.rb:100 0.008
Tags: @product
2:22.793
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 without a persistent partition and stopped at Tails Greeter's login screen 8.993
And I log in to a new session 15.377
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.972
And I plug USB drive "to_upgrade" 2.313
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.318
Then the running Tails is installed on USB drive "to_upgrade" 19.398
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.213
After features/support/hooks.rb:331 4.230
After features/support/hooks.rb:100 0.000
Tags: @product
1:40.983
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.202
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:32.997
Then all tps features from the old Tails version are active 1.385
And Tails is running from USB drive "to_upgrade" 0.291
And the boot device has safe access rights 2.727
And the expected persistent files created with the old Tails version are present in the filesystem 1.319
And all persistent directories from the old Tails version have safe access rights 2.059
After features/support/hooks.rb:331 0.872
After features/support/hooks.rb:100 0.007
4:43.696
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 9.701
And no SquashFS delta is installed 0.071
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.317
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.275
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.453
When the network is plugged 0.072
And Tor is ready 14.293
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.609
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.654
Given I shutdown Tails and wait for the computer to power off 7.773
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:35.436
Then Tails is running version 6.2~testoverlayfs 0.030
And all tps features are active 2.138
And the file system changes introduced in version 6.2~testoverlayfs are present 0.236
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.168
# 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.239
When the network is plugged 0.086
And Tor is ready 14.662
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.556
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.348
Given I shutdown Tails and wait for the computer to power off 7.716
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:34.956
Then Tails is running version 6.3~testoverlayfs 0.027
And all tps features are active 2.126
And the file system changes introduced in version 6.3~testoverlayfs are present 0.427
And only the 6.3~testoverlayfs SquashFS delta is installed 0.056
# 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.150
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.277
When the network is plugged 0.068
And Tor is ready 11.502
Then the Upgrader considers the system as up-to-date 0.176
# 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 5.473
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.495
After features/support/hooks.rb:331 0.941
After features/support/hooks.rb:100 0.015
22.978
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 9.607
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.307
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.058
But a current signing key is available on our website 0.000
When the network is plugged 0.086
And Tor is ready 11.112
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.743
After features/support/hooks.rb:331 1.064
After features/support/hooks.rb:100 0.000