Project Number Date
test_Tails_ISO_20979-pdfarranger 14 09 Jun 2025, 02:34

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 19:19.542 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:7.336
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.271
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 30.907
When I start Tails from USB drive "old" with network unplugged 1:30.886
Then the boot device has safe access rights 3.139
And Tails is running from USB drive "old" 0.344
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.109
And udev-watchdog is monitoring the correct device 0.318
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:330 6.853
After features/support/hooks.rb:100 0.007
Tags: @product
2:5.772
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:22.587
Then Tails is running from USB drive "old" 0.351
And I create a persistent partition 31.661
And I take note of which tps features are available 1.690
Then a Tails persistence partition exists on USB drive "old" 0.788
And I shutdown Tails and wait for the computer to power off 8.498
After features/support/hooks.rb:330 0.137
After features/support/hooks.rb:100 0.009
Tags: @product
2:53.516
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.206
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.788
Then Tails is running from USB drive "old" 0.519
And all tps features are active 1.964
When I write some files expected to persist 1.793
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.205
And all persistence configuration files have safe access rights 0.395
And all persistent directories from the old Tails version have safe access rights 2.730
And I take note of which tps features are available 0.451
And I shutdown Tails and wait for the computer to power off 4.378
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.082
After features/support/hooks.rb:330 0.161
After features/support/hooks.rb:100 0.008
Tags: @product
2:34.129
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.083
And I log in to a new session 23.630
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.659
And I plug USB drive "to_upgrade" 2.417
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.500
Then the running Tails is installed on USB drive "to_upgrade" 22.421
And I unplug USB drive "to_upgrade" 0.218
And I unplug USB drive "__internal" 0.196
After features/support/hooks.rb:330 1.957
After features/support/hooks.rb:100 0.000
Tags: @product
2:25.309
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.229
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.830
Then all tps features from the old Tails version are active 1.773
And Tails is running from USB drive "to_upgrade" 0.451
And the boot device has safe access rights 3.723
And the expected persistent files created with the old Tails version are present in the filesystem 1.457
And all persistent directories from the old Tails version have safe access rights 2.843
After features/support/hooks.rb:330 0.692
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:40.503
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.179
And no SquashFS delta is installed 0.410
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.451
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.115
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.283
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.477
When the network is plugged 0.116
And Tor is ready 17.820
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.393
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.108
Given I shutdown Tails and wait for the computer to power off 10.901
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.676
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.289
And the file system changes introduced in version 6.2~testoverlayfs are present 0.334
And only the 6.2~testoverlayfs SquashFS delta is installed 0.103
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.467
# 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.367
When the network is plugged 0.095
And Tor is ready 17.306
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.295
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.007
Given I shutdown Tails and wait for the computer to power off 4.470
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.867
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.996
And the file system changes introduced in version 6.3~testoverlayfs are present 0.691
And only the 6.3~testoverlayfs SquashFS delta is installed 0.089
# 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.775
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.635
When the network is plugged 0.077
And Tor is ready 18.667
Then the Upgrader considers the system as up-to-date 0.308
# 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 15.607
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.084
After features/support/hooks.rb:330 0.894
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
32.975
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.007
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.738
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.102
But a current signing key is available on our website 0.000
When the network is plugged 0.113
And Tor is ready 15.524
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.436
After features/support/hooks.rb:330 1.022
After features/support/hooks.rb:100 0.000