Project Number Date
test_Tails_ISO_devel 4035 24 Oct 2025, 12:19

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 16:41.112 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
2:8.265
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.205
And I create a 7200 MiB disk named "old" 0.060
And I plug USB drive "old" 1.043
And I write an old version of the Tails USB image to disk "old" 34.838
When I start Tails from USB drive "old" with network unplugged 1:27.902
Then the boot device has safe access rights 3.259
And Tails is running from USB drive "old" 0.338
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.262
And I unplug USB drive "old" 0.229
After features/support/hooks.rb:331 3.886
After features/support/hooks.rb:100 0.011
Tags: @product
2:7.980
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.215
And I start Tails from USB drive "old" with network unplugged and I login 1:27.432
Then Tails is running from USB drive "old" 0.323
And I create a persistent partition 30.203
And I take note of which tps features are available 1.304
Then a Tails persistence partition exists on USB drive "old" 0.673
And I shutdown Tails and wait for the computer to power off 7.827
After features/support/hooks.rb:331 0.625
After features/support/hooks.rb:100 0.011
Tags: @product
2:10.596
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:37.789
Then Tails is running from USB drive "old" 0.337
And all tps features are active 1.795
When I write some files expected to persist 1.954
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.300
And all persistence configuration files have safe access rights 0.472
And all persistent directories from the old Tails version have safe access rights 3.462
And I take note of which tps features are available 0.630
And I shutdown Tails and wait for the computer to power off 4.949
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.717
After features/support/hooks.rb:331 0.344
After features/support/hooks.rb:100 0.011
Tags: @product
2:42.974
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.196
And I log in to a new session 17.831
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.494
And I plug USB drive "to_upgrade" 3.157
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:44.629
Then the running Tails is installed on USB drive "to_upgrade" 22.185
And I unplug USB drive "to_upgrade" 0.215
And I unplug USB drive "__internal" 0.262
After features/support/hooks.rb:331 4.259
After features/support/hooks.rb:100 0.000
Tags: @product
1:49.796
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.186
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:40.447
Then all tps features from the old Tails version are active 1.584
And Tails is running from USB drive "to_upgrade" 0.289
And the boot device has safe access rights 3.090
And the expected persistent files created with the old Tails version are present in the filesystem 1.858
And all persistent directories from the old Tails version have safe access rights 2.339
After features/support/hooks.rb:331 0.714
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
5:6.267
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.339
And no SquashFS delta is installed 0.099
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.292
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.300
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.537
When the network is plugged 0.510
And Tor is ready 13.871
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.754
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.772
Given I shutdown Tails and wait for the computer to power off 11.238
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:42.547
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 5.010
And the file system changes introduced in version 6.2~testoverlayfs are present 0.276
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.289
# 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.261
When the network is plugged 0.502
And Tor is ready 12.150
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.634
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.814
Given I shutdown Tails and wait for the computer to power off 7.843
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:40.208
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.420
And the file system changes introduced in version 6.3~testoverlayfs are present 0.442
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.174
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.312
When the network is plugged 0.057
And Tor is ready 12.323
Then the Upgrader considers the system as up-to-date 0.201
# 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.392
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.450
After features/support/hooks.rb:331 2.864
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
35.232
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 19.049
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.294
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.081
But a current signing key is available on our website 0.000
When the network is plugged 0.524
And Tor is ready 13.136
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.087
After features/support/hooks.rb:331 3.832
After features/support/hooks.rb:100 0.000