Project Number Date
test_Tails_ISO_devel 3721 04 Mar 2025, 20:31

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:13.468 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:27.554
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.226
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 34.130
When I start Tails from USB drive "old" with network unplugged 1:47.972
Then the boot device has safe access rights 3.031
And Tails is running from USB drive "old" 0.397
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.310
And I unplug USB drive "old" 0.206
After features/support/hooks.rb:330 3.579
After features/support/hooks.rb:100 0.021
Tags: @product
2:16.047
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.208
And I start Tails from USB drive "old" with network unplugged and I login 1:31.714
Then Tails is running from USB drive "old" 0.438
And I create a persistent partition 32.241
And I take note of which tps features are available 1.889
Then a Tails persistence partition exists on USB drive "old" 0.876
And I shutdown Tails and wait for the computer to power off 8.678
After features/support/hooks.rb:330 0.269
After features/support/hooks.rb:100 0.022
Tags: @product
3:3.266
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.018
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.806
Then Tails is running from USB drive "old" 0.540
And all tps features are active 2.160
When I write some files expected to persist 2.183
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.265
And all persistence configuration files have safe access rights 0.472
And all persistent directories from the old Tails version have safe access rights 2.625
And I take note of which tps features are available 0.445
And I shutdown Tails and wait for the computer to power off 6.394
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.169
After features/support/hooks.rb:330 0.160
After features/support/hooks.rb:100 0.010
Tags: @product
2:31.801
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 without a persistent partition and stopped at Tails Greeter's login screen 11.200
And I log in to a new session 17.870
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.562
And I plug USB drive "to_upgrade" 2.366
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.203
Then the running Tails is installed on USB drive "to_upgrade" 22.166
And I unplug USB drive "to_upgrade" 0.227
And I unplug USB drive "__internal" 0.205
After features/support/hooks.rb:330 2.208
After features/support/hooks.rb:100 0.000
Tags: @product
2:26.589
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.187
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.378
Then all tps features from the old Tails version are active 2.676
And Tails is running from USB drive "to_upgrade" 0.357
And the boot device has safe access rights 3.935
And the expected persistent files created with the old Tails version are present in the filesystem 1.703
And all persistent directories from the old Tails version have safe access rights 3.350
After features/support/hooks.rb:330 1.210
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
6:49.215
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 14.330
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.417
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.124
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.453
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.481
When the network is plugged 0.073
And Tor is ready 20.445
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.108
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.541
Given I shutdown Tails and wait for the computer to power off 11.990
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.051
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.561
And the file system changes introduced in version 6.2~testoverlayfs are present 0.416
And only the 6.2~testoverlayfs SquashFS delta is installed 0.082
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.315
# 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.266
When the network is plugged 0.070
And Tor is ready 17.968
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.048
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.968
Given I shutdown Tails and wait for the computer to power off 6.379
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.089
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.221
And the file system changes introduced in version 6.3~testoverlayfs are present 0.716
And only the 6.3~testoverlayfs SquashFS delta is installed 0.129
# 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.320
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.275
When the network is plugged 0.079
And Tor is ready 19.078
Then the Upgrader considers the system as up-to-date 0.355
# 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.562
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.182
After features/support/hooks.rb:330 0.819
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
38.992
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.267
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.840
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the signing key used by the Upgrader is outdated 0.120
But a current signing key is available on our website 0.000
When the network is plugged 0.090
And Tor is ready 18.706
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.899
After features/support/hooks.rb:330 1.390
After features/support/hooks.rb:100 0.000