Project Number Date
test_Tails_ISO_codespell 1 17 Jun 2025, 22:15

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 28:39.049 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
3:15.432
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.228
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 44.213
When I start Tails from USB drive "old" with network unplugged 2:17.541
Then the boot device has safe access rights 10.518
And Tails is running from USB drive "old" 0.834
And there is no persistence partition on USB drive "old" 0.102
And process "udev-watchdog" is running 0.147
And udev-watchdog is monitoring the correct device 0.480
And I unplug USB drive "old" 0.270
After features/support/hooks.rb:330 3.810
After features/support/hooks.rb:100 0.009
Tags: @product
3:6.353
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login 2:2.593
Then Tails is running from USB drive "old" 0.511
And I create a persistent partition 47.734
And I take note of which tps features are available 3.417
Then a Tails persistence partition exists on USB drive "old" 1.155
And I shutdown Tails and wait for the computer to power off 10.740
After features/support/hooks.rb:330 2.300
After features/support/hooks.rb:100 0.154
Tags: @product
4:34.650
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.146
Given a computer 0.994
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:28.834
Then Tails is running from USB drive "old" 0.612
And all tps features are active 1.942
When I write some files expected to persist 3.020
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.416
And all persistence configuration files have safe access rights 0.502
And all persistent directories from the old Tails version have safe access rights 9.065
And I take note of which tps features are available 0.718
And I shutdown Tails and wait for the computer to power off 7.009
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 41.533
After features/support/hooks.rb:330 0.255
After features/support/hooks.rb:100 0.029
Tags: @product
3:39.159
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.015
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 17.589
And I log in to a new session 37.877
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.568
And I plug USB drive "to_upgrade" 2.755
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:59.797
Then the running Tails is installed on USB drive "to_upgrade" 38.939
And I unplug USB drive "to_upgrade" 0.281
And I unplug USB drive "__internal" 0.349
After features/support/hooks.rb:330 2.497
After features/support/hooks.rb:100 0.000
Tags: @product
3:17.378
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.203
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:2.588
Then all tps features from the old Tails version are active 5.479
And Tails is running from USB drive "to_upgrade" 0.804
And the boot device has safe access rights 3.805
And the expected persistent files created with the old Tails version are present in the filesystem 1.519
And all persistent directories from the old Tails version have safe access rights 2.977
After features/support/hooks.rb:330 1.264
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
9:50.206
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 20.505
And no SquashFS delta is installed 0.133
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.361
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.126
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.333
And the file system changes introduced in version 6.3~testoverlayfs are not present 1.144
When the network is plugged 0.681
And Tor is ready 52.425
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.640
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 19.645
Given I shutdown Tails and wait for the computer to power off 14.089
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:53.040
Then Tails is running version 6.2~testoverlayfs 1.306
And all tps features are active 6.634
And the file system changes introduced in version 6.2~testoverlayfs are present 0.601
And only the 6.2~testoverlayfs SquashFS delta is installed 0.236
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.588
# 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.382
When the network is plugged 0.083
And Tor is ready 25.885
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 13.794
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 18.557
Given I shutdown Tails and wait for the computer to power off 6.456
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:53.258
Then Tails is running version 6.3~testoverlayfs 0.034
And all tps features are active 2.932
And the file system changes introduced in version 6.3~testoverlayfs are present 0.534
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.318
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.373
When the network is plugged 0.106
And Tor is ready 25.080
Then the Upgrader considers the system as up-to-date 0.339
# 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 26.828
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.666
After features/support/hooks.rb:330 0.838
After features/support/hooks.rb:100 0.045
Tags: @product @automatic_upgrade
55.867
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 18.003
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.571
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.116
And the signing key used by the Upgrader is outdated 0.155
But a current signing key is available on our website 0.000
When the network is plugged 0.101
And Tor is ready 23.594
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 13.324
After features/support/hooks.rb:330 3.136
After features/support/hooks.rb:100 0.000