Project Number Date
test_Tails_ISO_stable 5479 24 Feb 2025, 12:27

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:18.902 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:25.315
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.047
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 30.911
When I start Tails from USB drive "old" with network unplugged 1:49.097
Then the boot device has safe access rights 3.024
And Tails is running from USB drive "old" 0.300
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.319
And I unplug USB drive "old" 0.198
After features/support/hooks.rb:330 7.311
After features/support/hooks.rb:100 0.008
Tags: @product
2:6.729
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.207
And I start Tails from USB drive "old" with network unplugged and I login 1:22.687
Then Tails is running from USB drive "old" 0.287
And I create a persistent partition 32.778
And I take note of which tps features are available 1.470
Then a Tails persistence partition exists on USB drive "old" 0.795
And I shutdown Tails and wait for the computer to power off 8.502
After features/support/hooks.rb:330 0.271
After features/support/hooks.rb:100 0.009
Tags: @product
2:50.271
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.125
Then Tails is running from USB drive "old" 0.401
And all tps features are active 1.957
When I write some files expected to persist 1.860
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.225
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.994
And I take note of which tps features are available 0.452
And I shutdown Tails and wait for the computer to power off 4.180
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.458
After features/support/hooks.rb:330 0.122
After features/support/hooks.rb:100 0.009
Tags: @product
2:32.329
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 10.769
And I log in to a new session 18.950
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.618
And I plug USB drive "to_upgrade" 2.376
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.149
Then the running Tails is installed on USB drive "to_upgrade" 24.051
And I unplug USB drive "to_upgrade" 0.210
And I unplug USB drive "__internal" 0.203
After features/support/hooks.rb:330 2.184
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.351
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.263
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.066
Then all tps features from the old Tails version are active 1.956
And Tails is running from USB drive "to_upgrade" 0.397
And the boot device has safe access rights 3.525
And the expected persistent files created with the old Tails version are present in the filesystem 1.526
And all persistent directories from the old Tails version have safe access rights 2.614
After features/support/hooks.rb:330 1.193
After features/support/hooks.rb:100 0.011
6:31.929
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 12.931
And no SquashFS delta is installed 0.315
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.488
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.095
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.269
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.459
When the network is plugged 0.068
And Tor is ready 23.192
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.602
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.174
Given I shutdown Tails and wait for the computer to power off 15.735
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.876
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.224
And the file system changes introduced in version 6.2~testoverlayfs are present 0.373
And only the 6.2~testoverlayfs SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.310
# 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.314
When the network is plugged 0.086
And Tor is ready 16.080
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.729
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.945
Given I shutdown Tails and wait for the computer to power off 4.481
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.204
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.496
And the file system changes introduced in version 6.3~testoverlayfs are present 0.529
And only the 6.3~testoverlayfs SquashFS delta is installed 0.095
# 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.301
When the network is plugged 0.087
And Tor is ready 20.541
Then the Upgrader considers the system as up-to-date 0.336
# 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.095
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.030
After features/support/hooks.rb:330 0.763
After features/support/hooks.rb:100 0.047
37.974
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.203
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.533
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.107
And the signing key used by the Upgrader is outdated 0.182
But a current signing key is available on our website 0.000
When the network is plugged 0.195
And Tor is ready 18.163
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.587
After features/support/hooks.rb:330 1.041
After features/support/hooks.rb:100 0.000