Project Number Date
test_Tails_ISO_stable 5452 12 Feb 2025, 08:50

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:25.277 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:21.548
Before features/support/hooks.rb:269 0.004
Given a computer 0.185
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 29.707
When I start Tails from USB drive "old" with network unplugged 1:46.499
Then the boot device has safe access rights 3.007
And Tails is running from USB drive "old" 0.325
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.115
And udev-watchdog is monitoring the correct device 0.325
And I unplug USB drive "old" 0.212
After features/support/hooks.rb:326 6.900
After features/support/hooks.rb:100 0.009
Tags: @product
2:13.105
Before features/support/hooks.rb:269 0.005
Given a computer 0.193
And I start Tails from USB drive "old" with network unplugged and I login 1:26.560
Then Tails is running from USB drive "old" 0.325
And I create a persistent partition 35.814
And I take note of which tps features are available 1.275
Then a Tails persistence partition exists on USB drive "old" 0.744
And I shutdown Tails and wait for the computer to power off 8.190
After features/support/hooks.rb:326 0.222
After features/support/hooks.rb:100 0.008
Tags: @product
2:54.731
Before features/support/hooks.rb:269 0.005
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.470
Then Tails is running from USB drive "old" 0.379
And all tps features are active 2.175
When I write some files expected to persist 1.838
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.213
And all persistence configuration files have safe access rights 0.416
And all persistent directories from the old Tails version have safe access rights 2.336
And I take note of which tps features are available 0.467
And I shutdown Tails and wait for the computer to power off 4.357
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.886
After features/support/hooks.rb:326 0.170
After features/support/hooks.rb:100 0.009
Tags: @product
2:33.529
Before features/support/hooks.rb:269 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 11.147
And I log in to a new session 17.759
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.500
And I plug USB drive "to_upgrade" 2.400
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.903
Then the running Tails is installed on USB drive "to_upgrade" 26.391
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.222
After features/support/hooks.rb:326 3.566
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.598
Before features/support/hooks.rb:269 0.006
Given a computer 0.188
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.355
Then all tps features from the old Tails version are active 1.623
And Tails is running from USB drive "to_upgrade" 0.347
And the boot device has safe access rights 3.394
And the expected persistent files created with the old Tails version are present in the filesystem 1.358
And all persistent directories from the old Tails version have safe access rights 2.330
After features/support/hooks.rb:326 0.627
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:28.111
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.135
And no SquashFS delta is installed 0.106
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.995
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.125
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.311
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.444
When the network is plugged 0.073
And Tor is ready 22.265
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.497
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.415
Given I shutdown Tails and wait for the computer to power off 8.837
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.416
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.119
And the file system changes introduced in version 6.2~testoverlayfs are present 0.416
And only the 6.2~testoverlayfs SquashFS delta is installed 0.102
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.452
# 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.298
When the network is plugged 0.091
And Tor is ready 16.800
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.407
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.094
Given I shutdown Tails and wait for the computer to power off 5.211
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.688
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.949
And the file system changes introduced in version 6.3~testoverlayfs are present 0.482
And only the 6.3~testoverlayfs SquashFS delta is installed 0.081
# 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.296
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.259
When the network is plugged 0.083
And Tor is ready 16.638
Then the Upgrader considers the system as up-to-date 0.314
# 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.700
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.967
After features/support/hooks.rb:326 1.060
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
40.653
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.292
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.428
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.077
But a current signing key is available on our website 0.000
When the network is plugged 0.067
And Tor is ready 20.334
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.393
After features/support/hooks.rb:326 0.753
After features/support/hooks.rb:100 0.000