Project Number Date
test_Tails_ISO_devel 3877 19 Jun 2025, 15:00

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 23:27.038 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:5.523
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.231
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 42.006
When I start Tails from USB drive "old" with network unplugged 2:16.928
Then the boot device has safe access rights 3.820
And Tails is running from USB drive "old" 0.372
And there is no persistence partition on USB drive "old" 0.141
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.432
And I unplug USB drive "old" 0.378
After features/support/hooks.rb:330 4.825
After features/support/hooks.rb:100 0.026
Tags: @product
2:37.946
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.019
Given a computer 0.453
And I start Tails from USB drive "old" with network unplugged and I login 1:47.594
Then Tails is running from USB drive "old" 0.562
And I create a persistent partition 37.318
And I take note of which tps features are available 2.697
Then a Tails persistence partition exists on USB drive "old" 0.806
And I shutdown Tails and wait for the computer to power off 8.512
After features/support/hooks.rb:330 1.191
After features/support/hooks.rb:100 0.028
Tags: @product
3:27.474
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.019
Given a computer 0.384
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:41.583
Then Tails is running from USB drive "old" 0.738
And all tps features are active 2.642
When I write some files expected to persist 2.318
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.319
And all persistence configuration files have safe access rights 0.362
And all persistent directories from the old Tails version have safe access rights 2.772
And I take note of which tps features are available 0.462
And I shutdown Tails and wait for the computer to power off 4.398
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 31.492
After features/support/hooks.rb:330 0.162
After features/support/hooks.rb:100 0.010
Tags: @product
2:48.300
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.475
And I log in to a new session 25.571
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.333
And I plug USB drive "to_upgrade" 2.658
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.807
Then the running Tails is installed on USB drive "to_upgrade" 27.023
And I unplug USB drive "to_upgrade" 0.233
And I unplug USB drive "__internal" 0.196
After features/support/hooks.rb:330 3.194
After features/support/hooks.rb:100 0.000
Tags: @product
2:45.281
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.023
Given a computer 0.521
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:32.427
Then all tps features from the old Tails version are active 1.725
And Tails is running from USB drive "to_upgrade" 0.353
And the boot device has safe access rights 3.728
And the expected persistent files created with the old Tails version are present in the filesystem 2.939
And all persistent directories from the old Tails version have safe access rights 3.585
After features/support/hooks.rb:330 1.659
After features/support/hooks.rb:100 0.020
7:51.465
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.344
And no SquashFS delta is installed 0.727
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.725
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.123
And the file system changes introduced in version 6.2~testoverlayfs are not present 1.131
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.831
When the network is plugged 0.081
And Tor is ready 26.413
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.289
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 16.120
Given I shutdown Tails and wait for the computer to power off 12.656
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:26.405
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 3.060
And the file system changes introduced in version 6.2~testoverlayfs are present 0.486
And only the 6.2~testoverlayfs SquashFS delta is installed 0.088
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.329
# 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.358
When the network is plugged 0.069
And Tor is ready 26.572
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.837
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.782
Given I shutdown Tails and wait for the computer to power off 8.302
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:27.286
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.505
And the file system changes introduced in version 6.3~testoverlayfs are present 0.699
And only the 6.3~testoverlayfs SquashFS delta is installed 0.194
# 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.480
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.600
When the network is plugged 0.064
And Tor is ready 20.047
Then the Upgrader considers the system as up-to-date 0.317
# 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.614
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.887
After features/support/hooks.rb:330 0.799
After features/support/hooks.rb:100 0.134
51.045
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.081
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.996
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.437
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.088
And the signing key used by the Upgrader is outdated 0.080
But a current signing key is available on our website 0.000
When the network is plugged 0.098
And Tor is ready 29.434
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.910
After features/support/hooks.rb:330 0.959
After features/support/hooks.rb:100 0.000