Project Number Date
test_Tails_ISO_stable 5686 29 May 2025, 14:16

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 19:44.695 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:3.323
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.176
And I create a 7200 MiB disk named "old" 0.107
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 32.706
When I start Tails from USB drive "old" with network unplugged 1:24.747
Then the boot device has safe access rights 3.409
And Tails is running from USB drive "old" 0.438
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.108
And udev-watchdog is monitoring the correct device 0.314
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:330 3.714
After features/support/hooks.rb:100 0.008
Tags: @product
2:10.349
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login 1:26.929
Then Tails is running from USB drive "old" 0.420
And I create a persistent partition 31.680
And I take note of which tps features are available 1.839
Then a Tails persistence partition exists on USB drive "old" 0.819
And I shutdown Tails and wait for the computer to power off 8.468
After features/support/hooks.rb:330 0.222
After features/support/hooks.rb:100 0.008
Tags: @product
2:56.546
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.175
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.027
Then Tails is running from USB drive "old" 0.330
And all tps features are active 2.134
When I write some files expected to persist 2.235
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.230
And all persistence configuration files have safe access rights 0.379
And all persistent directories from the old Tails version have safe access rights 2.629
And I take note of which tps features are available 0.457
And I shutdown Tails and wait for the computer to power off 6.584
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.359
After features/support/hooks.rb:330 0.156
After features/support/hooks.rb:100 0.010
Tags: @product
2:39.062
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 10.553
And I log in to a new session 18.814
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.844
And I plug USB drive "to_upgrade" 2.401
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.421
Then the running Tails is installed on USB drive "to_upgrade" 30.570
And I unplug USB drive "to_upgrade" 0.235
And I unplug USB drive "__internal" 0.219
After features/support/hooks.rb:330 2.571
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.083
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.241
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.965
Then all tps features from the old Tails version are active 2.160
And Tails is running from USB drive "to_upgrade" 0.383
And the boot device has safe access rights 3.376
And the expected persistent files created with the old Tails version are present in the filesystem 2.150
And all persistent directories from the old Tails version have safe access rights 2.805
After features/support/hooks.rb:330 1.495
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:53.941
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.467
And no SquashFS delta is installed 0.071
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.695
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.107
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.327
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.440
When the network is plugged 0.153
And Tor is ready 51.066
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.607
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.853
Given I shutdown Tails and wait for the computer to power off 8.703
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.800
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.434
And the file system changes introduced in version 6.2~testoverlayfs are present 0.382
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.303
# 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.287
When the network is plugged 0.067
And Tor is ready 15.996
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.096
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.261
Given I shutdown Tails and wait for the computer to power off 6.361
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.751
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.899
And the file system changes introduced in version 6.3~testoverlayfs are present 0.491
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.301
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.361
When the network is plugged 0.069
And Tor is ready 15.538
Then the Upgrader considers the system as up-to-date 0.411
# 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.536
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.934
After features/support/hooks.rb:330 0.824
After features/support/hooks.rb:100 0.038
Tags: @product @automatic_upgrade
37.388
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 10.867
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.384
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.109
But a current signing key is available on our website 0.000
When the network is plugged 0.104
And Tor is ready 17.883
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.979
After features/support/hooks.rb:330 0.977
After features/support/hooks.rb:100 0.000