Project Number Date
test_Tails_ISO_devel 3869 15 Jun 2025, 13:25

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 22:24.462 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.679
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.210
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 37.120
When I start Tails from USB drive "old" with network unplugged 1:45.931
Then the boot device has safe access rights 4.017
And Tails is running from USB drive "old" 0.409
And there is no persistence partition on USB drive "old" 0.101
And process "udev-watchdog" is running 0.242
And udev-watchdog is monitoring the correct device 0.362
And I unplug USB drive "old" 0.182
After features/support/hooks.rb:330 6.987
After features/support/hooks.rb:100 0.012
Tags: @product
2:30.491
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.252
And I start Tails from USB drive "old" with network unplugged and I login 1:38.344
Then Tails is running from USB drive "old" 0.331
And I create a persistent partition 36.583
And I take note of which tps features are available 3.866
Then a Tails persistence partition exists on USB drive "old" 1.511
And I shutdown Tails and wait for the computer to power off 9.604
After features/support/hooks.rb:330 0.218
After features/support/hooks.rb:100 0.010
Tags: @product
3:19.660
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.363
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:33.315
Then Tails is running from USB drive "old" 1.799
And all tps features are active 3.233
When I write some files expected to persist 2.317
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.247
And all persistence configuration files have safe access rights 0.417
And all persistent directories from the old Tails version have safe access rights 2.907
And I take note of which tps features are available 0.450
And I shutdown Tails and wait for the computer to power off 4.401
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 30.205
After features/support/hooks.rb:330 0.184
After features/support/hooks.rb:100 0.016
Tags: @product
2:56.338
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 without a persistent partition and stopped at Tails Greeter's login screen 11.743
And I log in to a new session 24.969
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.454
And I plug USB drive "to_upgrade" 2.535
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.243
Then the running Tails is installed on USB drive "to_upgrade" 32.063
And I unplug USB drive "to_upgrade" 1.013
And I unplug USB drive "__internal" 0.315
After features/support/hooks.rb:330 2.622
After features/support/hooks.rb:100 0.000
Tags: @product
2:41.605
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given a computer 0.295
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:29.323
Then all tps features from the old Tails version are active 1.971
And Tails is running from USB drive "to_upgrade" 0.492
And the boot device has safe access rights 4.147
And the expected persistent files created with the old Tails version are present in the filesystem 1.910
And all persistent directories from the old Tails version have safe access rights 3.462
After features/support/hooks.rb:330 1.420
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:43.062
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 13.094
And no SquashFS delta is installed 0.416
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.513
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
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.652
When the network is plugged 0.318
And Tor is ready 24.539
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.941
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 15.456
Given I shutdown Tails and wait for the computer to power off 10.531
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:26.282
Then Tails is running version 6.2~testoverlayfs 0.029
And all tps features are active 2.203
And the file system changes introduced in version 6.2~testoverlayfs are present 0.321
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.311
# 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.305
When the network is plugged 0.081
And Tor is ready 22.297
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.818
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.343
Given I shutdown Tails and wait for the computer to power off 4.858
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:27.555
Then Tails is running version 6.3~testoverlayfs 0.083
And all tps features are active 3.051
And the file system changes introduced in version 6.3~testoverlayfs are present 0.723
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.325
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.318
When the network is plugged 0.072
And Tor is ready 20.636
Then the Upgrader considers the system as up-to-date 0.336
# 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.748
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.406
After features/support/hooks.rb:330 0.775
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
43.623
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.562
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.516
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.081
And the signing key used by the Upgrader is outdated 0.081
But a current signing key is available on our website 0.000
When the network is plugged 0.077
And Tor is ready 21.276
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.026
After features/support/hooks.rb:330 1.073
After features/support/hooks.rb:100 0.000