Project Number Date
test_Tails_ISO_codespell 6 18 Jun 2025, 22:36

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:22.619 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:29.416
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.017
Given a computer 0.246
And I create a 7200 MiB disk named "old" 0.092
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 39.348
When I start Tails from USB drive "old" with network unplugged 1:44.026
Then the boot device has safe access rights 3.402
And Tails is running from USB drive "old" 0.415
And there is no persistence partition on USB drive "old" 0.123
And process "udev-watchdog" is running 0.107
And udev-watchdog is monitoring the correct device 0.390
And I unplug USB drive "old" 0.214
After features/support/hooks.rb:330 3.879
After features/support/hooks.rb:100 0.073
Tags: @product
2:32.129
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.168
Given a computer 1.134
And I start Tails from USB drive "old" with network unplugged and I login 1:40.585
Then Tails is running from USB drive "old" 0.741
And I create a persistent partition 34.908
And I take note of which tps features are available 2.574
Then a Tails persistence partition exists on USB drive "old" 1.886
And I shutdown Tails and wait for the computer to power off 10.298
After features/support/hooks.rb:330 0.168
After features/support/hooks.rb:100 0.009
Tags: @product
3:14.730
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:24.783
Then Tails is running from USB drive "old" 0.666
And all tps features are active 3.208
When I write some files expected to persist 2.910
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.603
And all persistence configuration files have safe access rights 0.994
And all persistent directories from the old Tails version have safe access rights 3.242
And I take note of which tps features are available 0.405
And I shutdown Tails and wait for the computer to power off 6.447
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 31.268
After features/support/hooks.rb:330 0.235
After features/support/hooks.rb:100 0.010
Tags: @product
2:57.047
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 10.998
And I log in to a new session 24.689
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.993
And I plug USB drive "to_upgrade" 2.779
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:45.154
Then the running Tails is installed on USB drive "to_upgrade" 29.742
And I unplug USB drive "to_upgrade" 0.243
And I unplug USB drive "__internal" 0.446
After features/support/hooks.rb:330 2.567
After features/support/hooks.rb:100 0.000
Tags: @product
2:31.868
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.441
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:20.136
Then all tps features from the old Tails version are active 2.565
And Tails is running from USB drive "to_upgrade" 0.317
And the boot device has safe access rights 3.651
And the expected persistent files created with the old Tails version are present in the filesystem 1.766
And all persistent directories from the old Tails version have safe access rights 2.989
After features/support/hooks.rb:330 2.621
After features/support/hooks.rb:100 0.018
7:49.713
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.415
And no SquashFS delta is installed 0.160
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.436
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.108
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.371
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.421
When the network is plugged 0.122
And Tor is ready 23.795
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.763
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 16.776
Given I shutdown Tails and wait for the computer to power off 8.761
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.819
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.194
And the file system changes introduced in version 6.2~testoverlayfs are present 0.361
And only the 6.2~testoverlayfs SquashFS delta is installed 0.108
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.414
# 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.488
When the network is plugged 0.225
And Tor is ready 22.635
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.399
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.593
Given I shutdown Tails and wait for the computer to power off 7.679
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.924
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 3.814
And the file system changes introduced in version 6.3~testoverlayfs are present 0.629
And only the 6.3~testoverlayfs SquashFS delta is installed 0.151
# 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.471
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.602
When the network is plugged 0.140
And Tor is ready 46.968
Then the Upgrader considers the system as up-to-date 0.360
# 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.415
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.150
After features/support/hooks.rb:330 0.731
After features/support/hooks.rb:100 0.022
47.713
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 13.568
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.556
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.119
And the signing key used by the Upgrader is outdated 0.263
But a current signing key is available on our website 0.000
When the network is plugged 0.110
And Tor is ready 23.604
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.489
After features/support/hooks.rb:330 1.252
After features/support/hooks.rb:100 0.000