Project Number Date
test_Tails_ISO_feature-arti 104 02 Jul 2025, 18:03

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 24:47.467 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:14.195
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.249
And I create a 7200 MiB disk named "old" 0.059
And I plug USB drive "old" 1.154
And I write an old version of the Tails USB image to disk "old" 35.147
When I start Tails from USB drive "old" with network unplugged 1:31.252
Then the boot device has safe access rights 4.123
And Tails is running from USB drive "old" 0.868
And there is no persistence partition on USB drive "old" 0.207
And process "udev-watchdog" is running 0.321
And udev-watchdog is monitoring the correct device 0.508
And I unplug USB drive "old" 0.303
After features/support/hooks.rb:330 3.968
After features/support/hooks.rb:100 0.012
Tags: @product
2:26.653
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.217
And I start Tails from USB drive "old" with network unplugged and I login 1:35.759
Then Tails is running from USB drive "old" 0.472
And I create a persistent partition 37.628
And I take note of which tps features are available 3.067
Then a Tails persistence partition exists on USB drive "old" 0.921
And I shutdown Tails and wait for the computer to power off 8.587
After features/support/hooks.rb:330 0.190
After features/support/hooks.rb:100 0.011
Tags: @product
3:35.215
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:40.836
Then Tails is running from USB drive "old" 1.393
And all tps features are active 2.530
When I write some files expected to persist 6.832
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.279
And all persistence configuration files have safe access rights 0.554
And all persistent directories from the old Tails version have safe access rights 3.911
And I take note of which tps features are available 0.556
And I shutdown Tails and wait for the computer to power off 4.372
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 33.765
After features/support/hooks.rb:330 0.170
After features/support/hooks.rb:100 0.025
Tags: @product
2:56.823
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.026
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.091
And I log in to a new session 25.203
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.237
And I plug USB drive "to_upgrade" 2.468
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.585
Then the running Tails is installed on USB drive "to_upgrade" 32.697
And I unplug USB drive "to_upgrade" 0.284
And I unplug USB drive "__internal" 0.254
After features/support/hooks.rb:330 3.135
After features/support/hooks.rb:100 0.000
Tags: @product
2:43.476
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.323
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:28.525
Then all tps features from the old Tails version are active 2.260
And Tails is running from USB drive "to_upgrade" 1.485
And the boot device has safe access rights 5.735
And the expected persistent files created with the old Tails version are present in the filesystem 2.600
And all persistent directories from the old Tails version have safe access rights 2.545
After features/support/hooks.rb:330 0.671
After features/support/hooks.rb:100 0.011
9:56.586
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 with a persistent partition enabled and logged in 13.791
And no SquashFS delta is installed 0.126
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.518
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.112
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.475
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.657
When the network is plugged 0.084
And Tor is ready 38.392
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.625
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.189
Given I shutdown Tails and wait for the computer to power off 9.353
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:33.407
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 3.201
And the file system changes introduced in version 6.2~testoverlayfs are present 0.364
And only the 6.2~testoverlayfs SquashFS delta is installed 0.096
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.343
# 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.448
When the network is plugged 0.082
And Tor is ready 20.487
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 11.906
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.904
Given I shutdown Tails and wait for the computer to power off 1:16.262
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:35.213
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.425
And the file system changes introduced in version 6.3~testoverlayfs are present 0.622
And only the 6.3~testoverlayfs SquashFS delta is installed 0.102
# 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.378
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.356
When the network is plugged 0.087
And Tor is ready 50.424
Then the Upgrader considers the system as up-to-date 0.334
# 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 18.818
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.952
After features/support/hooks.rb:330 0.737
After features/support/hooks.rb:100 0.019
54.516
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 with a persistent partition enabled and logged in 13.232
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.689
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.077
But a current signing key is available on our website 0.000
When the network is plugged 0.079
And Tor is ready 29.630
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 10.746
After features/support/hooks.rb:330 1.524
After features/support/hooks.rb:100 0.000