Project Number Date
test_Tails_ISO_stable 5518 17 Mar 2025, 13:01

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 20:46.631 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:26.894
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 1.936
And I create a 7200 MiB disk named "old" 0.620
And I plug USB drive "old" 1.300
And I write an old version of the Tails USB image to disk "old" 35.165
When I start Tails from USB drive "old" with network unplugged 1:43.601
Then the boot device has safe access rights 3.200
And Tails is running from USB drive "old" 0.396
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.308
And I unplug USB drive "old" 0.197
After features/support/hooks.rb:330 7.198
After features/support/hooks.rb:100 0.008
Tags: @product
2:22.495
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.227
And I start Tails from USB drive "old" with network unplugged and I login 1:39.172
Then Tails is running from USB drive "old" 0.294
And I create a persistent partition 31.492
And I take note of which tps features are available 1.936
Then a Tails persistence partition exists on USB drive "old" 0.847
And I shutdown Tails and wait for the computer to power off 8.525
After features/support/hooks.rb:330 0.175
After features/support/hooks.rb:100 0.008
Tags: @product
2:54.004
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.087
Then Tails is running from USB drive "old" 0.410
And all tps features are active 2.321
When I write some files expected to persist 2.132
# 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.502
And all persistent directories from the old Tails version have safe access rights 2.597
And I take note of which tps features are available 0.471
And I shutdown Tails and wait for the computer to power off 6.361
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.558
After features/support/hooks.rb:330 0.141
After features/support/hooks.rb:100 0.009
Tags: @product
2:32.605
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.970
And I log in to a new session 19.118
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.790
And I plug USB drive "to_upgrade" 2.363
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.979
Then the running Tails is installed on USB drive "to_upgrade" 21.968
And I unplug USB drive "to_upgrade" 0.191
And I unplug USB drive "__internal" 0.225
After features/support/hooks.rb:330 2.109
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.069
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.233
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.658
Then all tps features from the old Tails version are active 1.862
And Tails is running from USB drive "to_upgrade" 0.383
And the boot device has safe access rights 4.125
And the expected persistent files created with the old Tails version are present in the filesystem 1.430
And all persistent directories from the old Tails version have safe access rights 2.375
After features/support/hooks.rb:330 1.174
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
7:27.817
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.015
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.949
And no SquashFS delta is installed 0.336
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.476
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.289
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.495
When the network is plugged 0.071
And Tor is ready 23.594
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.124
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.959
Given I shutdown Tails and wait for the computer to power off 8.999
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.002
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.478
And the file system changes introduced in version 6.2~testoverlayfs are present 0.398
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.377
# 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.310
When the network is plugged 0.145
And Tor is ready 48.332
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.638
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.909
Given I shutdown Tails and wait for the computer to power off 4.469
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:21.268
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.745
And the file system changes introduced in version 6.3~testoverlayfs are present 0.558
And only the 6.3~testoverlayfs SquashFS delta is installed 0.092
# 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.282
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.431
When the network is plugged 0.095
And Tor is ready 17.149
Then the Upgrader considers the system as up-to-date 0.324
# 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.100
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.220
After features/support/hooks.rb:330 0.844
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
42.744
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.447
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.646
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.099
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.116
And Tor is ready 22.162
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.162
After features/support/hooks.rb:330 1.071
After features/support/hooks.rb:100 0.000