Project Number Date
test_Tails_ISO_codespell 8 22 Jun 2025, 11:16

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 21:33.332 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:12.369
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.194
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 30.640
When I start Tails from USB drive "old" with network unplugged 1:35.183
Then the boot device has safe access rights 3.987
And Tails is running from USB drive "old" 0.510
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.361
And I unplug USB drive "old" 0.237
After features/support/hooks.rb:330 3.905
After features/support/hooks.rb:100 0.039
Tags: @product
2:22.989
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login 1:34.394
Then Tails is running from USB drive "old" 0.601
And I create a persistent partition 35.010
And I take note of which tps features are available 2.543
Then a Tails persistence partition exists on USB drive "old" 0.938
And I shutdown Tails and wait for the computer to power off 9.306
After features/support/hooks.rb:330 0.205
After features/support/hooks.rb:100 0.011
Tags: @product
3:4.611
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.440
Then Tails is running from USB drive "old" 0.350
And all tps features are active 2.111
When I write some files expected to persist 2.502
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.223
And all persistence configuration files have safe access rights 0.633
And all persistent directories from the old Tails version have safe access rights 3.245
And I take note of which tps features are available 0.498
And I shutdown Tails and wait for the computer to power off 4.800
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.600
After features/support/hooks.rb:330 0.115
After features/support/hooks.rb:100 0.009
Tags: @product
2:47.510
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.952
And I log in to a new session 22.437
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.699
And I plug USB drive "to_upgrade" 2.604
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.207
Then the running Tails is installed on USB drive "to_upgrade" 31.177
And I unplug USB drive "to_upgrade" 0.220
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:330 2.505
After features/support/hooks.rb:100 0.000
Tags: @product
2:38.490
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.022
Given a computer 0.258
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:25.603
Then all tps features from the old Tails version are active 2.301
And Tails is running from USB drive "to_upgrade" 0.421
And the boot device has safe access rights 3.734
And the expected persistent files created with the old Tails version are present in the filesystem 3.019
And all persistent directories from the old Tails version have safe access rights 3.151
After features/support/hooks.rb:330 1.615
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:46.982
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 12.088
And no SquashFS delta is installed 0.192
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.657
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.283
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.454
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.699
When the network is plugged 0.110
And Tor is ready 23.603
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.515
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.975
Given I shutdown Tails and wait for the computer to power off 9.561
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:26.993
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.534
And the file system changes introduced in version 6.2~testoverlayfs are present 0.454
And only the 6.2~testoverlayfs SquashFS delta is installed 0.090
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.398
# 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.322
When the network is plugged 0.099
And Tor is ready 47.161
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.752
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.366
Given I shutdown Tails and wait for the computer to power off 4.684
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.774
Then Tails is running version 6.3~testoverlayfs 0.023
And all tps features are active 2.986
And the file system changes introduced in version 6.3~testoverlayfs are present 0.595
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.324
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.292
When the network is plugged 0.076
And Tor is ready 22.544
Then the Upgrader considers the system as up-to-date 0.349
# 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.365
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.558
After features/support/hooks.rb:330 0.973
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
40.380
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.343
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.314
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the signing key used by the Upgrader is outdated 0.154
But a current signing key is available on our website 0.000
When the network is plugged 0.131
And Tor is ready 21.010
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.356
After features/support/hooks.rb:330 0.763
After features/support/hooks.rb:100 0.000