Project Number Date
test_Tails_ISO_stable 5640 11 May 2025, 12:51

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:5.232 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.571
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.197
And I create a 7200 MiB disk named "old" 0.054
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 31.444
When I start Tails from USB drive "old" with network unplugged 1:35.056
Then the boot device has safe access rights 3.556
And Tails is running from USB drive "old" 0.463
And there is no persistence partition on USB drive "old" 0.105
And process "udev-watchdog" is running 0.120
And udev-watchdog is monitoring the correct device 0.300
And I unplug USB drive "old" 0.213
After features/support/hooks.rb:330 3.596
After features/support/hooks.rb:100 0.009
Tags: @product
2:15.557
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login 1:29.974
Then Tails is running from USB drive "old" 0.310
And I create a persistent partition 33.055
And I take note of which tps features are available 2.507
Then a Tails persistence partition exists on USB drive "old" 0.833
And I shutdown Tails and wait for the computer to power off 8.680
After features/support/hooks.rb:330 0.256
After features/support/hooks.rb:100 0.009
Tags: @product
3:11.543
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.220
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:29.629
Then Tails is running from USB drive "old" 0.812
And all tps features are active 2.106
When I write some files expected to persist 2.504
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.249
And all persistence configuration files have safe access rights 0.537
And all persistent directories from the old Tails version have safe access rights 2.869
And I take note of which tps features are available 0.663
And I shutdown Tails and wait for the computer to power off 6.568
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.381
After features/support/hooks.rb:330 0.207
After features/support/hooks.rb:100 0.012
Tags: @product
2:39.978
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.610
And I log in to a new session 20.847
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.112
And I plug USB drive "to_upgrade" 2.569
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.374
Then the running Tails is installed on USB drive "to_upgrade" 24.968
And I unplug USB drive "to_upgrade" 0.246
And I unplug USB drive "__internal" 0.247
After features/support/hooks.rb:330 2.828
After features/support/hooks.rb:100 0.000
Tags: @product
2:28.572
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given a computer 0.257
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:16.523
Then all tps features from the old Tails version are active 2.023
And Tails is running from USB drive "to_upgrade" 0.391
And the boot device has safe access rights 3.847
And the expected persistent files created with the old Tails version are present in the filesystem 2.578
And all persistent directories from the old Tails version have safe access rights 2.950
After features/support/hooks.rb:330 1.492
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:35.568
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 17.888
And no SquashFS delta is installed 0.208
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.515
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.087
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.425
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.563
When the network is plugged 0.083
And Tor is ready 23.271
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.697
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.717
Given I shutdown Tails and wait for the computer to power off 9.001
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:32.377
Then Tails is running version 6.2~testoverlayfs 0.022
And all tps features are active 2.658
And the file system changes introduced in version 6.2~testoverlayfs are present 0.401
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.339
# 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.386
When the network is plugged 0.080
And Tor is ready 21.728
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.581
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.566
Given I shutdown Tails and wait for the computer to power off 6.762
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.792
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.671
And the file system changes introduced in version 6.3~testoverlayfs are present 1.072
And only the 6.3~testoverlayfs SquashFS delta is installed 0.151
# 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.349
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.502
When the network is plugged 0.090
And Tor is ready 22.460
Then the Upgrader considers the system as up-to-date 0.338
# 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.535
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.130
After features/support/hooks.rb:330 0.886
After features/support/hooks.rb:100 0.031
Tags: @product @automatic_upgrade
41.440
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.833
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.537
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.094
And the signing key used by the Upgrader is outdated 0.089
But a current signing key is available on our website 0.000
When the network is plugged 0.096
And Tor is ready 21.215
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.573
After features/support/hooks.rb:330 0.870
After features/support/hooks.rb:100 0.000