Project Number Date
test_Tails_ISO_codespell 7 19 Jun 2025, 11:10

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 27:31.094 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:56.524
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.202
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.064
And I write an old version of the Tails USB image to disk "old" 39.417
When I start Tails from USB drive "old" with network unplugged 2:5.383
Then the boot device has safe access rights 7.930
And Tails is running from USB drive "old" 1.285
And there is no persistence partition on USB drive "old" 0.198
And process "udev-watchdog" is running 0.217
And udev-watchdog is monitoring the correct device 0.405
And I unplug USB drive "old" 0.373
After features/support/hooks.rb:330 4.024
After features/support/hooks.rb:100 0.010
Tags: @product
2:49.825
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.225
And I start Tails from USB drive "old" with network unplugged and I login 1:56.640
Then Tails is running from USB drive "old" 0.662
And I create a persistent partition 39.756
And I take note of which tps features are available 2.794
Then a Tails persistence partition exists on USB drive "old" 0.814
And I shutdown Tails and wait for the computer to power off 8.931
After features/support/hooks.rb:330 1.991
After features/support/hooks.rb:100 0.122
Tags: @product
3:56.356
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.035
Given a computer 1.032
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:5.551
Then Tails is running from USB drive "old" 0.678
And all tps features are active 1.978
When I write some files expected to persist 1.805
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.309
And all persistence configuration files have safe access rights 0.566
And all persistent directories from the old Tails version have safe access rights 3.102
And I take note of which tps features are available 0.529
And I shutdown Tails and wait for the computer to power off 6.932
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 33.870
After features/support/hooks.rb:330 1.749
After features/support/hooks.rb:100 0.185
Tags: @product
3:15.946
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.063
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 14.700
And I log in to a new session 33.796
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.505
And I plug USB drive "to_upgrade" 2.581
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:50.528
Then the running Tails is installed on USB drive "to_upgrade" 32.397
And I unplug USB drive "to_upgrade" 0.238
And I unplug USB drive "__internal" 0.197
After features/support/hooks.rb:330 3.830
After features/support/hooks.rb:100 0.000
Tags: @product
3:10.531
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.019
Given a computer 0.727
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:52.472
Then all tps features from the old Tails version are active 2.640
And Tails is running from USB drive "to_upgrade" 0.496
And the boot device has safe access rights 9.294
And the expected persistent files created with the old Tails version are present in the filesystem 2.195
And all persistent directories from the old Tails version have safe access rights 2.705
After features/support/hooks.rb:330 1.791
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
10:31.929
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 18.792
And no SquashFS delta is installed 0.108
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.315
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.076
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.289
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.674
When the network is plugged 0.161
And Tor is ready 34.476
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.786
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 18.309
Given I shutdown Tails and wait for the computer to power off 1:38.359
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:48.721
Then Tails is running version 6.2~testoverlayfs 0.414
And all tps features are active 5.124
And the file system changes introduced in version 6.2~testoverlayfs are present 0.907
And only the 6.2~testoverlayfs SquashFS delta is installed 0.137
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.419
# 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.755
When the network is plugged 0.117
And Tor is ready 23.284
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.899
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 16.820
Given I shutdown Tails and wait for the computer to power off 8.463
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:44.175
Then Tails is running version 6.3~testoverlayfs 0.021
And all tps features are active 4.064
And the file system changes introduced in version 6.3~testoverlayfs are present 0.502
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.396
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.333
When the network is plugged 0.082
And Tor is ready 23.353
Then the Upgrader considers the system as up-to-date 0.358
# 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 21.796
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 6.357
After features/support/hooks.rb:330 1.554
After features/support/hooks.rb:100 0.078
Tags: @product @automatic_upgrade
49.979
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.037
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.994
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.293
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 0.084
But a current signing key is available on our website 0.000
When the network is plugged 0.080
And Tor is ready 30.459
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.001
After features/support/hooks.rb:330 1.272
After features/support/hooks.rb:100 0.000