Project Number Date
test_Tails_ISO_stable 5664 20 May 2025, 13:04

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:33.430 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:23.971
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.209
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.063
And I write an old version of the Tails USB image to disk "old" 31.580
When I start Tails from USB drive "old" with network unplugged 1:46.470
Then the boot device has safe access rights 3.460
And Tails is running from USB drive "old" 0.402
And there is no persistence partition on USB drive "old" 0.089
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.364
And I unplug USB drive "old" 0.185
After features/support/hooks.rb:330 3.520
After features/support/hooks.rb:100 0.067
Tags: @product
2:19.455
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.015
Given a computer 0.287
And I start Tails from USB drive "old" with network unplugged and I login 1:34.816
Then Tails is running from USB drive "old" 0.362
And I create a persistent partition 32.286
And I take note of which tps features are available 2.290
Then a Tails persistence partition exists on USB drive "old" 0.920
And I shutdown Tails and wait for the computer to power off 8.490
After features/support/hooks.rb:330 0.182
After features/support/hooks.rb:100 0.010
Tags: @product
3:13.083
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.336
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:31.735
Then Tails is running from USB drive "old" 0.362
And all tps features are active 2.517
When I write some files expected to persist 1.952
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.224
And all persistence configuration files have safe access rights 0.387
And all persistent directories from the old Tails version have safe access rights 2.603
And I take note of which tps features are available 0.483
And I shutdown Tails and wait for the computer to power off 6.247
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.233
After features/support/hooks.rb:330 0.111
After features/support/hooks.rb:100 0.008
Tags: @product
2:42.651
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.904
And I log in to a new session 21.280
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.792
And I plug USB drive "to_upgrade" 2.473
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.297
Then the running Tails is installed on USB drive "to_upgrade" 28.490
And I unplug USB drive "to_upgrade" 0.197
And I unplug USB drive "__internal" 0.215
After features/support/hooks.rb:330 3.606
After features/support/hooks.rb:100 0.000
Tags: @product
2:44.208
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Given a computer 0.247
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:31.906
Then all tps features from the old Tails version are active 2.476
And Tails is running from USB drive "to_upgrade" 0.504
And the boot device has safe access rights 4.285
And the expected persistent files created with the old Tails version are present in the filesystem 1.798
And all persistent directories from the old Tails version have safe access rights 2.988
After features/support/hooks.rb:330 1.408
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:30.099
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.078
And no SquashFS delta is installed 0.206
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.530
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.349
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.492
When the network is plugged 0.072
And Tor is ready 28.951
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.543
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.770
Given I shutdown Tails and wait for the computer to power off 8.962
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:30.332
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.640
And the file system changes introduced in version 6.2~testoverlayfs are present 0.376
And only the 6.2~testoverlayfs SquashFS delta is installed 0.093
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.364
# 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.401
When the network is plugged 0.065
And Tor is ready 19.345
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.833
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.861
Given I shutdown Tails and wait for the computer to power off 4.785
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.222
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.091
And the file system changes introduced in version 6.3~testoverlayfs are present 0.658
And only the 6.3~testoverlayfs SquashFS delta is installed 0.088
# 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.332
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.339
When the network is plugged 0.070
And Tor is ready 20.600
Then the Upgrader considers the system as up-to-date 0.329
# 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 16.218
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.001
After features/support/hooks.rb:330 0.895
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
39.960
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.300
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.673
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.137
And the signing key used by the Upgrader is outdated 0.189
But a current signing key is available on our website 0.000
When the network is plugged 0.074
And Tor is ready 20.043
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.540
After features/support/hooks.rb:330 0.749
After features/support/hooks.rb:100 0.000