Project Number Date
test_Tails_ISO_codespell 18 02 Jul 2025, 10:44

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 22:12.013 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:35.149
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.179
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 34.306
When I start Tails from USB drive "old" with network unplugged 1:52.456
Then the boot device has safe access rights 5.678
And Tails is running from USB drive "old" 0.512
And there is no persistence partition on USB drive "old" 0.147
And process "udev-watchdog" is running 0.154
And udev-watchdog is monitoring the correct device 0.421
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:330 4.141
After features/support/hooks.rb:100 0.008
Tags: @product
2:22.469
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.201
And I start Tails from USB drive "old" with network unplugged and I login 1:33.126
Then Tails is running from USB drive "old" 0.388
And I create a persistent partition 36.087
And I take note of which tps features are available 2.898
Then a Tails persistence partition exists on USB drive "old" 1.065
And I shutdown Tails and wait for the computer to power off 8.700
After features/support/hooks.rb:330 0.187
After features/support/hooks.rb:100 0.009
Tags: @product
3:13.312
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.224
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:28.835
Then Tails is running from USB drive "old" 0.426
And all tps features are active 2.352
When I write some files expected to persist 2.250
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.287
And all persistence configuration files have safe access rights 0.536
And all persistent directories from the old Tails version have safe access rights 2.489
And I take note of which tps features are available 0.439
And I shutdown Tails and wait for the computer to power off 4.526
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 30.943
After features/support/hooks.rb:330 0.217
After features/support/hooks.rb:100 0.022
Tags: @product
2:46.727
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.016
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.368
And I log in to a new session 22.612
And I clone USB drive "old" to a new USB drive "to_upgrade" 3.152
And I plug USB drive "to_upgrade" 2.573
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.588
Then the running Tails is installed on USB drive "to_upgrade" 28.967
And I unplug USB drive "to_upgrade" 0.207
And I unplug USB drive "__internal" 0.255
After features/support/hooks.rb:330 3.839
After features/support/hooks.rb:100 0.000
Tags: @product
2:47.471
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.177
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:35.324
Then all tps features from the old Tails version are active 1.827
And Tails is running from USB drive "to_upgrade" 0.442
And the boot device has safe access rights 4.045
And the expected persistent files created with the old Tails version are present in the filesystem 2.466
And all persistent directories from the old Tails version have safe access rights 3.188
After features/support/hooks.rb:330 1.887
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:43.174
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 27.587
And no SquashFS delta is installed 0.839
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.526
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.346
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.869
When the network is plugged 0.103
And Tor is ready 36.622
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.055
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.669
Given I shutdown Tails and wait for the computer to power off 11.096
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:17.446
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.633
And the file system changes introduced in version 6.2~testoverlayfs are present 0.410
And only the 6.2~testoverlayfs SquashFS delta is installed 0.084
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.308
# 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.428
When the network is plugged 0.072
And Tor is ready 18.783
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.225
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 13.825
Given I shutdown Tails and wait for the computer to power off 6.704
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.021
Then Tails is running version 6.3~testoverlayfs 0.074
And all tps features are active 2.200
And the file system changes introduced in version 6.3~testoverlayfs are present 0.609
And only the 6.3~testoverlayfs SquashFS delta is installed 0.087
# 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.397
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.376
When the network is plugged 0.067
And Tor is ready 21.883
Then the Upgrader considers the system as up-to-date 0.320
# 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.979
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.449
After features/support/hooks.rb:330 0.772
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
43.707
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.107
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.397
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the signing key used by the Upgrader is outdated 0.093
But a current signing key is available on our website 0.000
When the network is plugged 0.071
And Tor is ready 24.311
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.662
After features/support/hooks.rb:330 0.875
After features/support/hooks.rb:100 0.000