Project Number Date
test_Tails_ISO_feature-arti 101 29 Jun 2025, 17:41

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 20:23.793 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:9.227
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.056
Given a computer 0.287
And I create a 7200 MiB disk named "old" 0.085
And I plug USB drive "old" 1.070
And I write an old version of the Tails USB image to disk "old" 29.666
When I start Tails from USB drive "old" with network unplugged 1:33.322
Then the boot device has safe access rights 3.599
And Tails is running from USB drive "old" 0.403
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.348
And I unplug USB drive "old" 0.264
After features/support/hooks.rb:330 7.151
After features/support/hooks.rb:100 0.009
Tags: @product
2:16.212
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.174
And I start Tails from USB drive "old" with network unplugged and I login 1:29.995
Then Tails is running from USB drive "old" 0.355
And I create a persistent partition 33.925
And I take note of which tps features are available 2.128
Then a Tails persistence partition exists on USB drive "old" 0.874
And I shutdown Tails and wait for the computer to power off 8.759
After features/support/hooks.rb:330 0.180
After features/support/hooks.rb:100 0.010
Tags: @product
3:6.253
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.319
Then Tails is running from USB drive "old" 0.792
And all tps features are active 2.340
When I write some files expected to persist 2.496
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.402
And all persistence configuration files have safe access rights 0.395
And all persistent directories from the old Tails version have safe access rights 3.279
And I take note of which tps features are available 0.548
And I shutdown Tails and wait for the computer to power off 6.826
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.654
After features/support/hooks.rb:330 0.148
After features/support/hooks.rb:100 0.010
Tags: @product
2:38.958
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.384
And I log in to a new session 21.481
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.464
And I plug USB drive "to_upgrade" 2.545
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.637
Then the running Tails is installed on USB drive "to_upgrade" 27.980
And I unplug USB drive "to_upgrade" 0.244
And I unplug USB drive "__internal" 0.219
After features/support/hooks.rb:330 4.133
After features/support/hooks.rb:100 0.000
Tags: @product
2:29.272
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.219
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:17.875
Then all tps features from the old Tails version are active 3.094
And Tails is running from USB drive "to_upgrade" 0.348
And the boot device has safe access rights 3.469
And the expected persistent files created with the old Tails version are present in the filesystem 1.590
And all persistent directories from the old Tails version have safe access rights 2.675
After features/support/hooks.rb:330 0.598
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:4.018
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.596
And no SquashFS delta is installed 0.149
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.508
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.120
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.375
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.836
When the network is plugged 0.082
And Tor is ready 24.195
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.192
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.497
Given I shutdown Tails and wait for the computer to power off 8.684
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:19.546
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.422
And the file system changes introduced in version 6.2~testoverlayfs are present 0.682
And only the 6.2~testoverlayfs SquashFS delta is installed 0.215
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.614
# 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.543
When the network is plugged 0.074
And Tor is ready 19.727
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.416
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.002
Given I shutdown Tails and wait for the computer to power off 6.613
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.921
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.062
And the file system changes introduced in version 6.3~testoverlayfs are present 0.672
And only the 6.3~testoverlayfs SquashFS delta is installed 0.081
# 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.336
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.326
When the network is plugged 0.089
And Tor is ready 21.366
Then the Upgrader considers the system as up-to-date 0.359
# 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 16.106
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.567
After features/support/hooks.rb:330 0.686
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
39.851
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 11.184
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.678
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 0.112
But a current signing key is available on our website 0.000
When the network is plugged 0.104
And Tor is ready 20.495
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.228
After features/support/hooks.rb:330 1.139
After features/support/hooks.rb:100 0.000