Project Number Date
test_Tails_ISO_devel 3903 08 Jul 2025, 18:12

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:55.060 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
3:26.411
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.860
And I create a 7200 MiB disk named "old" 0.281
And I plug USB drive "old" 1.463
And I write an old version of the Tails USB image to disk "old" 48.930
When I start Tails from USB drive "old" with network unplugged 2:24.315
Then the boot device has safe access rights 6.670
And Tails is running from USB drive "old" 1.689
And there is no persistence partition on USB drive "old" 0.152
And process "udev-watchdog" is running 0.299
And udev-watchdog is monitoring the correct device 1.124
And I unplug USB drive "old" 0.622
After features/support/hooks.rb:330 5.780
After features/support/hooks.rb:100 0.014
Tags: @product
3:25.561
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given a computer 0.280
And I start Tails from USB drive "old" with network unplugged and I login 2:20.491
Then Tails is running from USB drive "old" 0.628
And I create a persistent partition 47.670
And I take note of which tps features are available 4.478
Then a Tails persistence partition exists on USB drive "old" 1.613
And I shutdown Tails and wait for the computer to power off 10.399
After features/support/hooks.rb:330 0.277
After features/support/hooks.rb:100 0.014
Tags: @product
4:34.701
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.238
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:31.330
Then Tails is running from USB drive "old" 0.880
And all tps features are active 2.821
When I write some files expected to persist 2.825
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.398
And all persistence configuration files have safe access rights 0.790
And all persistent directories from the old Tails version have safe access rights 5.815
And I take note of which tps features are available 0.789
And I shutdown Tails and wait for the computer to power off 6.437
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 42.373
After features/support/hooks.rb:330 0.144
After features/support/hooks.rb:100 0.016
Tags: @product
3:20.441
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 15.277
And I log in to a new session 28.381
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.871
And I plug USB drive "to_upgrade" 5.323
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:47.267
Then the running Tails is installed on USB drive "to_upgrade" 40.874
And I unplug USB drive "to_upgrade" 0.214
And I unplug USB drive "__internal" 0.231
After features/support/hooks.rb:330 2.454
After features/support/hooks.rb:100 0.000
Tags: @product
3:7.179
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.317
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:54.155
Then all tps features from the old Tails version are active 1.995
And Tails is running from USB drive "to_upgrade" 0.342
And the boot device has safe access rights 3.742
And the expected persistent files created with the old Tails version are present in the filesystem 1.699
And all persistent directories from the old Tails version have safe access rights 4.925
After features/support/hooks.rb:330 3.844
After features/support/hooks.rb:100 0.029
Tags: @product @automatic_upgrade
9:10.603
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.019
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.013
And no SquashFS delta is installed 0.651
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.857
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.716
And the file system changes introduced in version 6.2~testoverlayfs are not present 1.298
And the file system changes introduced in version 6.3~testoverlayfs are not present 1.366
When the network is plugged 0.471
And Tor is ready 26.409
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 15.132
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 17.568
Given I shutdown Tails and wait for the computer to power off 11.890
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:2.316
Then Tails is running version 6.2~testoverlayfs 0.263
And all tps features are active 5.937
And the file system changes introduced in version 6.2~testoverlayfs are present 0.585
And only the 6.2~testoverlayfs SquashFS delta is installed 0.164
# 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.809
When the network is plugged 0.107
And Tor is ready 26.205
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 13.102
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 19.296
Given I shutdown Tails and wait for the computer to power off 6.884
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:31.437
Then Tails is running version 6.3~testoverlayfs 0.092
And all tps features are active 3.405
And the file system changes introduced in version 6.3~testoverlayfs are present 0.869
And only the 6.3~testoverlayfs SquashFS delta is installed 0.121
# 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.342
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.266
When the network is plugged 0.086
And Tor is ready 23.556
Then the Upgrader considers the system as up-to-date 0.565
# 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 20.579
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.720
After features/support/hooks.rb:330 0.928
After features/support/hooks.rb:100 0.125
Tags: @product @automatic_upgrade
50.160
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.021
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 16.639
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.348
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.112
And the signing key used by the Upgrader is outdated 0.093
But a current signing key is available on our website 0.000
When the network is plugged 0.101
And Tor is ready 23.321
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.543
After features/support/hooks.rb:330 0.898
After features/support/hooks.rb:100 0.000