Project Number Date
test_Tails_ISO_devel 3872 17 Jun 2025, 22:53

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 27:20.571 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:57.553
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.032
Given a computer 0.427
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.077
And I write an old version of the Tails USB image to disk "old" 50.487
When I start Tails from USB drive "old" with network unplugged 2:1.127
Then the boot device has safe access rights 3.242
And Tails is running from USB drive "old" 0.358
And there is no persistence partition on USB drive "old" 0.080
And process "udev-watchdog" is running 0.118
And udev-watchdog is monitoring the correct device 0.375
And I unplug USB drive "old" 0.207
After features/support/hooks.rb:330 3.756
After features/support/hooks.rb:100 0.017
Tags: @product
3:9.799
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.212
And I start Tails from USB drive "old" with network unplugged and I login 1:59.907
Then Tails is running from USB drive "old" 0.425
And I create a persistent partition 47.851
And I take note of which tps features are available 4.615
Then a Tails persistence partition exists on USB drive "old" 0.973
And I shutdown Tails and wait for the computer to power off 15.814
After features/support/hooks.rb:330 0.346
After features/support/hooks.rb:100 0.036
Tags: @product
4:20.409
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.021
Given a computer 0.598
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:14.081
Then Tails is running from USB drive "old" 3.514
And all tps features are active 3.474
When I write some files expected to persist 2.023
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.241
And all persistence configuration files have safe access rights 0.435
And all persistent directories from the old Tails version have safe access rights 2.897
And I take note of which tps features are available 0.612
And I shutdown Tails and wait for the computer to power off 10.451
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 42.079
After features/support/hooks.rb:330 0.169
After features/support/hooks.rb:100 0.009
Tags: @product
3:20.100
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 18.465
And I log in to a new session 26.053
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.582
And I plug USB drive "to_upgrade" 2.514
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:54.055
Then the running Tails is installed on USB drive "to_upgrade" 35.750
And I unplug USB drive "to_upgrade" 0.225
And I unplug USB drive "__internal" 0.453
After features/support/hooks.rb:330 3.182
After features/support/hooks.rb:100 0.000
Tags: @product
3:11.563
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.228
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:55.737
Then all tps features from the old Tails version are active 2.426
And Tails is running from USB drive "to_upgrade" 0.391
And the boot device has safe access rights 3.814
And the expected persistent files created with the old Tails version are present in the filesystem 2.130
And all persistent directories from the old Tails version have safe access rights 6.833
After features/support/hooks.rb:330 1.621
After features/support/hooks.rb:100 0.095
Tags: @product @automatic_upgrade
9:25.590
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.022
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 20.075
And no SquashFS delta is installed 0.358
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.635
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.161
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.514
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.967
When the network is plugged 0.148
And Tor is ready 1:1.280
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.609
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 16.783
Given I shutdown Tails and wait for the computer to power off 12.270
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:52.889
Then Tails is running version 6.2~testoverlayfs 0.023
And all tps features are active 3.025
And the file system changes introduced in version 6.2~testoverlayfs are present 0.612
And only the 6.2~testoverlayfs SquashFS delta is installed 0.131
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.508
# 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.339
When the network is plugged 0.149
And Tor is ready 28.630
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.849
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 14.090
Given I shutdown Tails and wait for the computer to power off 7.437
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:37.548
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.772
And the file system changes introduced in version 6.3~testoverlayfs are present 1.151
And only the 6.3~testoverlayfs SquashFS delta is installed 0.106
# 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.338
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.343
When the network is plugged 0.087
And Tor is ready 29.598
Then the Upgrader considers the system as up-to-date 0.960
# 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 22.637
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.535
After features/support/hooks.rb:330 0.742
After features/support/hooks.rb:100 0.027
Tags: @product @automatic_upgrade
55.555
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 13.105
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.960
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.156
And the signing key used by the Upgrader is outdated 0.139
But a current signing key is available on our website 0.000
When the network is plugged 0.104
And Tor is ready 27.256
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 13.832
After features/support/hooks.rb:330 1.608
After features/support/hooks.rb:100 0.000