Project Number Date
test_Tails_ISO_codespell 4 18 Jun 2025, 17:22

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:32.532 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:18.638
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.285
And I create a 7200 MiB disk named "old" 0.058
And I plug USB drive "old" 1.069
And I write an old version of the Tails USB image to disk "old" 53.464
When I start Tails from USB drive "old" with network unplugged 2:18.624
Then the boot device has safe access rights 3.574
And Tails is running from USB drive "old" 0.409
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.111
And udev-watchdog is monitoring the correct device 0.514
And I unplug USB drive "old" 0.446
After features/support/hooks.rb:330 5.518
After features/support/hooks.rb:100 0.330
Tags: @product
3:28.204
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.280
Given a computer 0.961
And I start Tails from USB drive "old" with network unplugged and I login 2:20.046
Then Tails is running from USB drive "old" 3.412
And I create a persistent partition 46.741
And I take note of which tps features are available 2.940
Then a Tails persistence partition exists on USB drive "old" 1.055
And I shutdown Tails and wait for the computer to power off 13.046
After features/support/hooks.rb:330 0.304
After features/support/hooks.rb:100 0.010
Tags: @product
4:38.377
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.252
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:29.891
Then Tails is running from USB drive "old" 3.749
And all tps features are active 5.766
When I write some files expected to persist 2.067
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.255
And all persistence configuration files have safe access rights 0.463
And all persistent directories from the old Tails version have safe access rights 3.145
And I take note of which tps features are available 0.675
And I shutdown Tails and wait for the computer to power off 9.675
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 42.434
After features/support/hooks.rb:330 0.220
After features/support/hooks.rb:100 0.009
Tags: @product
3:23.525
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.340
And I log in to a new session 32.859
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.559
And I plug USB drive "to_upgrade" 2.867
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:58.772
Then the running Tails is installed on USB drive "to_upgrade" 36.714
And I unplug USB drive "to_upgrade" 0.217
And I unplug USB drive "__internal" 0.194
After features/support/hooks.rb:330 3.798
After features/support/hooks.rb:100 0.000
Tags: @product
3:22.517
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given a computer 0.318
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:2.525
Then all tps features from the old Tails version are active 7.958
And Tails is running from USB drive "to_upgrade" 1.148
And the boot device has safe access rights 4.923
And the expected persistent files created with the old Tails version are present in the filesystem 2.058
And all persistent directories from the old Tails version have safe access rights 3.585
After features/support/hooks.rb:330 4.654
After features/support/hooks.rb:100 0.140
Tags: @product @automatic_upgrade
9:21.855
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.102
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 17.492
And no SquashFS delta is installed 1.194
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.080
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.153
And the file system changes introduced in version 6.2~testoverlayfs are not present 1.310
And the file system changes introduced in version 6.3~testoverlayfs are not present 1.343
When the network is plugged 0.303
And Tor is ready 26.523
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 15.357
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 19.447
Given I shutdown Tails and wait for the computer to power off 10.959
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:56.770
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 3.012
And the file system changes introduced in version 6.2~testoverlayfs are present 0.424
And only the 6.2~testoverlayfs SquashFS delta is installed 0.122
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.602
# 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 1.989
When the network is plugged 0.149
And Tor is ready 24.884
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.702
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 15.614
Given I shutdown Tails and wait for the computer to power off 6.410
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:54.469
Then Tails is running version 6.3~testoverlayfs 0.022
And all tps features are active 2.349
And the file system changes introduced in version 6.3~testoverlayfs are present 0.532
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.303
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.267
When the network is plugged 0.062
And Tor is ready 23.721
Then the Upgrader considers the system as up-to-date 0.593
# 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 24.822
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.765
After features/support/hooks.rb:330 1.329
After features/support/hooks.rb:100 0.064
Tags: @product @automatic_upgrade
59.414
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.541
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.248
And the signing key used by the Upgrader is outdated 0.213
But a current signing key is available on our website 0.000
When the network is plugged 0.152
And Tor is ready 29.070
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 14.112
After features/support/hooks.rb:330 1.515
After features/support/hooks.rb:100 0.000