Project Number Date
test_Tails_ISO_devel 3845 30 May 2025, 13:28

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 20:15.519 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:16.721
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.191
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 30.214
When I start Tails from USB drive "old" with network unplugged 1:39.678
Then the boot device has safe access rights 3.238
And Tails is running from USB drive "old" 0.374
And there is no persistence partition on USB drive "old" 0.212
And process "udev-watchdog" is running 0.249
And udev-watchdog is monitoring the correct device 1.263
And I unplug USB drive "old" 0.208
After features/support/hooks.rb:330 3.610
After features/support/hooks.rb:100 0.019
Tags: @product
2:23.952
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.235
And I start Tails from USB drive "old" with network unplugged and I login 1:38.223
Then Tails is running from USB drive "old" 0.303
And I create a persistent partition 33.017
And I take note of which tps features are available 2.539
Then a Tails persistence partition exists on USB drive "old" 0.835
And I shutdown Tails and wait for the computer to power off 8.796
After features/support/hooks.rb:330 0.234
After features/support/hooks.rb:100 0.014
Tags: @product
3:1.792
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.229
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.750
Then Tails is running from USB drive "old" 0.347
And all tps features are active 1.991
When I write some files expected to persist 1.841
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.266
And all persistence configuration files have safe access rights 0.429
And all persistent directories from the old Tails version have safe access rights 2.727
And I take note of which tps features are available 0.821
And I shutdown Tails and wait for the computer to power off 6.883
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.503
After features/support/hooks.rb:330 0.156
After features/support/hooks.rb:100 0.010
Tags: @product
2:42.141
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 12.966
And I log in to a new session 20.983
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.819
And I plug USB drive "to_upgrade" 2.520
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.142
Then the running Tails is installed on USB drive "to_upgrade" 25.253
And I unplug USB drive "to_upgrade" 0.221
And I unplug USB drive "__internal" 0.233
After features/support/hooks.rb:330 2.320
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.021
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.238
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.072
Then all tps features from the old Tails version are active 1.773
And Tails is running from USB drive "to_upgrade" 0.331
And the boot device has safe access rights 3.425
And the expected persistent files created with the old Tails version are present in the filesystem 1.551
And all persistent directories from the old Tails version have safe access rights 2.629
After features/support/hooks.rb:330 0.945
After features/support/hooks.rb:100 0.015
6:45.747
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.237
And no SquashFS delta is installed 0.113
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.324
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.076
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.369
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.623
When the network is plugged 0.070
And Tor is ready 23.140
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.277
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.211
Given I shutdown Tails and wait for the computer to power off 8.987
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.375
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.182
And the file system changes introduced in version 6.2~testoverlayfs are present 0.300
And only the 6.2~testoverlayfs SquashFS delta is installed 0.085
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.293
# 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.255
When the network is plugged 0.086
And Tor is ready 16.959
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.322
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.037
Given I shutdown Tails and wait for the computer to power off 4.453
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.494
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.206
And the file system changes introduced in version 6.3~testoverlayfs are present 0.552
And only the 6.3~testoverlayfs SquashFS delta is installed 0.082
# 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.328
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.313
When the network is plugged 0.094
And Tor is ready 19.723
Then the Upgrader considers the system as up-to-date 0.352
# 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 17.078
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.703
After features/support/hooks.rb:330 0.789
After features/support/hooks.rb:100 0.022
41.143
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 11.036
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.532
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.111
But a current signing key is available on our website 0.000
When the network is plugged 0.069
And Tor is ready 22.133
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.206
After features/support/hooks.rb:330 0.945
After features/support/hooks.rb:100 0.000