Project Number Date
test_Tails_ISO_test-suite-options 5 21 Jun 2025, 21:49

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:19.178 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:0.214
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.217
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.067
And I write an old version of the Tails USB image to disk "old" 43.151
When I start Tails from USB drive "old" with network unplugged 2:10.937
Then the boot device has safe access rights 3.719
And Tails is running from USB drive "old" 0.394
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.104
And udev-watchdog is monitoring the correct device 0.309
And I unplug USB drive "old" 0.201
After features/support/hooks.rb:330 9.340
After features/support/hooks.rb:100 0.023
Tags: @product
3:6.433
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.016
Given a computer 0.784
And I start Tails from USB drive "old" with network unplugged and I login 2:2.842
Then Tails is running from USB drive "old" 0.711
And I create a persistent partition 47.259
And I take note of which tps features are available 2.804
Then a Tails persistence partition exists on USB drive "old" 1.173
And I shutdown Tails and wait for the computer to power off 10.858
After features/support/hooks.rb:330 0.274
After features/support/hooks.rb:100 0.010
Tags: @product
4:15.459
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.369
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:17.177
Then Tails is running from USB drive "old" 1.196
And all tps features are active 2.686
When I write some files expected to persist 1.903
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.228
And all persistence configuration files have safe access rights 0.417
And all persistent directories from the old Tails version have safe access rights 3.416
And I take note of which tps features are available 0.539
And I shutdown Tails and wait for the computer to power off 8.324
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 39.200
After features/support/hooks.rb:330 0.815
After features/support/hooks.rb:100 0.032
Tags: @product
3:20.619
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.038
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.619
And I log in to a new session 32.223
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.333
And I plug USB drive "to_upgrade" 2.506
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:51.731
Then the running Tails is installed on USB drive "to_upgrade" 32.947
And I unplug USB drive "to_upgrade" 6.539
And I unplug USB drive "__internal" 0.717
After features/support/hooks.rb:330 8.671
After features/support/hooks.rb:100 0.000
Tags: @product
3:15.985
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.217
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:59.138
Then all tps features from the old Tails version are active 2.539
And Tails is running from USB drive "to_upgrade" 0.481
And the boot device has safe access rights 8.475
And the expected persistent files created with the old Tails version are present in the filesystem 2.115
And all persistent directories from the old Tails version have safe access rights 3.017
After features/support/hooks.rb:330 0.679
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
9:34.518
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 13.955
And no SquashFS delta is installed 0.506
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.558
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.189
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.616
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.634
When the network is plugged 0.100
And Tor is ready 27.644
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 13.245
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 20.317
Given I shutdown Tails and wait for the computer to power off 16.574
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:50.770
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 4.839
And the file system changes introduced in version 6.2~testoverlayfs are present 4.129
And only the 6.2~testoverlayfs SquashFS delta is installed 0.753
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.627
# 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.512
When the network is plugged 0.140
And Tor is ready 57.498
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.096
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.959
Given I shutdown Tails and wait for the computer to power off 7.977
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:35.166
Then Tails is running version 6.3~testoverlayfs 0.200
And all tps features are active 7.907
And the file system changes introduced in version 6.3~testoverlayfs are present 0.893
And only the 6.3~testoverlayfs SquashFS delta is installed 0.109
# 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.358
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.420
When the network is plugged 0.137
And Tor is ready 25.317
Then the Upgrader considers the system as up-to-date 0.436
# 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 22.162
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 8.743
After features/support/hooks.rb:330 0.861
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
45.946
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.028
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.713
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.424
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.069
But a current signing key is available on our website 0.000
When the network is plugged 0.079
And Tor is ready 28.648
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.959
After features/support/hooks.rb:330 0.883
After features/support/hooks.rb:100 0.000