Project Number Date
test_Tails_ISO_devel 3844 29 May 2025, 14:56

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:31.406 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:29.632
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.017
Given a computer 0.244
And I create a 7200 MiB disk named "old" 0.085
And I plug USB drive "old" 1.101
And I write an old version of the Tails USB image to disk "old" 50.100
When I start Tails from USB drive "old" with network unplugged 1:33.696
Then the boot device has safe access rights 3.234
And Tails is running from USB drive "old" 0.352
And there is no persistence partition on USB drive "old" 0.089
And process "udev-watchdog" is running 0.117
And udev-watchdog is monitoring the correct device 0.381
And I unplug USB drive "old" 0.228
After features/support/hooks.rb:330 3.917
After features/support/hooks.rb:100 0.014
Tags: @product
2:17.871
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.015
Given a computer 0.295
And I start Tails from USB drive "old" with network unplugged and I login 1:34.515
Then Tails is running from USB drive "old" 0.370
And I create a persistent partition 32.804
And I take note of which tps features are available 2.305
Then a Tails persistence partition exists on USB drive "old" 0.881
And I shutdown Tails and wait for the computer to power off 6.697
After features/support/hooks.rb:330 0.147
After features/support/hooks.rb:100 0.011
Tags: @product
3:9.203
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:30.314
Then Tails is running from USB drive "old" 0.411
And all tps features are active 2.297
When I write some files expected to persist 1.747
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.294
And all persistence configuration files have safe access rights 0.458
And all persistent directories from the old Tails version have safe access rights 2.637
And I take note of which tps features are available 0.609
And I shutdown Tails and wait for the computer to power off 4.410
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.818
After features/support/hooks.rb:330 0.188
After features/support/hooks.rb:100 0.013
Tags: @product
3:4.583
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 17.376
And I log in to a new session 26.330
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.119
And I plug USB drive "to_upgrade" 2.475
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:47.475
Then the running Tails is installed on USB drive "to_upgrade" 28.337
And I unplug USB drive "to_upgrade" 0.228
And I unplug USB drive "__internal" 0.239
After features/support/hooks.rb:330 3.790
After features/support/hooks.rb:100 0.000
Tags: @product
2:37.729
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.217
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:26.089
Then all tps features from the old Tails version are active 1.941
And Tails is running from USB drive "to_upgrade" 0.414
And the boot device has safe access rights 4.058
And the expected persistent files created with the old Tails version are present in the filesystem 2.028
And all persistent directories from the old Tails version have safe access rights 2.979
After features/support/hooks.rb:330 1.220
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
7:9.668
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 16.017
And no SquashFS delta is installed 0.199
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.410
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.285
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.551
When the network is plugged 0.070
And Tor is ready 22.578
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.485
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.914
Given I shutdown Tails and wait for the computer to power off 11.429
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:18.697
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.704
And the file system changes introduced in version 6.2~testoverlayfs are present 0.399
And only the 6.2~testoverlayfs SquashFS delta is installed 0.097
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.374
# 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.371
When the network is plugged 0.081
And Tor is ready 21.175
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.928
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.876
Given I shutdown Tails and wait for the computer to power off 4.830
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.042
Then Tails is running version 6.3~testoverlayfs 0.022
And all tps features are active 2.417
And the file system changes introduced in version 6.3~testoverlayfs are present 0.601
And only the 6.3~testoverlayfs SquashFS delta is installed 0.089
# 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.330
When the network is plugged 0.091
And Tor is ready 20.324
Then the Upgrader considers the system as up-to-date 0.314
# 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.457
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.063
After features/support/hooks.rb:330 0.797
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
42.716
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.974
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.451
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.157
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.107
And Tor is ready 21.409
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.521
After features/support/hooks.rb:330 0.926
After features/support/hooks.rb:100 0.000