Project Number Date
test_Tails_ISO_devel 3788 27 Apr 2025, 13:09

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:13.811 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:35.826
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.192
And I create a 7200 MiB disk named "old" 0.054
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 35.678
When I start Tails from USB drive "old" with network unplugged 1:54.172
Then the boot device has safe access rights 3.579
And Tails is running from USB drive "old" 0.372
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.101
And udev-watchdog is monitoring the correct device 0.337
And I unplug USB drive "old" 0.219
After features/support/hooks.rb:330 3.759
After features/support/hooks.rb:100 0.011
Tags: @product
2:13.981
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.229
And I start Tails from USB drive "old" with network unplugged and I login 1:29.477
Then Tails is running from USB drive "old" 0.343
And I create a persistent partition 31.983
And I take note of which tps features are available 2.384
Then a Tails persistence partition exists on USB drive "old" 0.798
And I shutdown Tails and wait for the computer to power off 8.764
After features/support/hooks.rb:330 0.165
After features/support/hooks.rb:100 0.011
Tags: @product
3:11.341
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.254
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:30.116
Then Tails is running from USB drive "old" 0.405
And all tps features are active 2.260
When I write some files expected to persist 2.250
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.365
And all persistence configuration files have safe access rights 0.441
And all persistent directories from the old Tails version have safe access rights 2.700
And I take note of which tps features are available 0.470
And I shutdown Tails and wait for the computer to power off 6.503
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.571
After features/support/hooks.rb:330 0.158
After features/support/hooks.rb:100 0.009
Tags: @product
2:40.598
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 13.493
And I log in to a new session 21.722
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.692
And I plug USB drive "to_upgrade" 2.492
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.218
Then the running Tails is installed on USB drive "to_upgrade" 23.262
And I unplug USB drive "to_upgrade" 0.285
And I unplug USB drive "__internal" 0.430
After features/support/hooks.rb:330 1.162
After features/support/hooks.rb:100 0.000
Tags: @product
2:37.448
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.220
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:27.196
Then all tps features from the old Tails version are active 2.244
And Tails is running from USB drive "to_upgrade" 0.345
And the boot device has safe access rights 3.402
And the expected persistent files created with the old Tails version are present in the filesystem 1.421
And all persistent directories from the old Tails version have safe access rights 2.617
After features/support/hooks.rb:330 1.759
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
7:56.957
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.393
And no SquashFS delta is installed 0.103
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.325
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.082
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.456
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.508
When the network is plugged 0.070
And Tor is ready 20.884
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.784
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.011
Given I shutdown Tails and wait for the computer to power off 1:25.125
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.357
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.610
And the file system changes introduced in version 6.2~testoverlayfs are present 0.300
And only the 6.2~testoverlayfs SquashFS delta is installed 0.076
# 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.254
When the network is plugged 0.133
And Tor is ready 19.963
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.805
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 12.385
Given I shutdown Tails and wait for the computer to power off 4.322
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.901
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.313
And the file system changes introduced in version 6.3~testoverlayfs are present 0.577
And only the 6.3~testoverlayfs SquashFS delta is installed 0.094
# 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.355
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.297
When the network is plugged 0.065
And Tor is ready 18.589
Then the Upgrader considers the system as up-to-date 0.331
# 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.717
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.392
After features/support/hooks.rb:330 0.833
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
57.656
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 9.827
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.334
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the signing key used by the Upgrader is outdated 0.065
But a current signing key is available on our website 0.000
When the network is plugged 0.088
And Tor is ready 46.679
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.617
After features/support/hooks.rb:330 0.868
After features/support/hooks.rb:100 0.000