Project Number Date
test_Tails_ISO_stable 5421 27 Jan 2025, 19: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 19:22.898 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:18.050
Before features/support/hooks.rb:269 0.006
Given a computer 0.175
And I create a 7200 MiB disk named "old" 0.040
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 31.682
When I start Tails from USB drive "old" with network unplugged 1:40.844
Then the boot device has safe access rights 3.206
And Tails is running from USB drive "old" 0.309
And there is no persistence partition on USB drive "old" 0.082
And process "udev-watchdog" is running 0.145
And udev-watchdog is monitoring the correct device 0.323
And I unplug USB drive "old" 0.184
After features/support/hooks.rb:326 7.101
After features/support/hooks.rb:100 0.012
Tags: @product
2:17.368
Before features/support/hooks.rb:269 0.004
Given a computer 0.206
And I start Tails from USB drive "old" with network unplugged and I login 1:33.381
Then Tails is running from USB drive "old" 0.302
And I create a persistent partition 32.675
And I take note of which tps features are available 1.497
Then a Tails persistence partition exists on USB drive "old" 0.848
And I shutdown Tails and wait for the computer to power off 8.455
After features/support/hooks.rb:326 0.181
After features/support/hooks.rb:100 0.009
Tags: @product
2:52.014
Before features/support/hooks.rb:269 0.004
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.160
Then Tails is running from USB drive "old" 0.651
And all tps features are active 1.979
When I write some files expected to persist 1.961
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.332
And all persistence configuration files have safe access rights 0.442
And all persistent directories from the old Tails version have safe access rights 2.500
And I take note of which tps features are available 0.429
And I shutdown Tails and wait for the computer to power off 4.147
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.226
After features/support/hooks.rb:326 0.121
After features/support/hooks.rb:100 0.007
Tags: @product
2:31.816
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.465
And I log in to a new session 18.515
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.174
And I plug USB drive "to_upgrade" 2.385
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.563
Then the running Tails is installed on USB drive "to_upgrade" 24.315
And I unplug USB drive "to_upgrade" 0.188
And I unplug USB drive "__internal" 0.207
After features/support/hooks.rb:326 2.004
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.093
Before features/support/hooks.rb:269 0.005
Given a computer 0.177
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.586
Then all tps features from the old Tails version are active 1.646
And Tails is running from USB drive "to_upgrade" 0.325
And the boot device has safe access rights 3.430
And the expected persistent files created with the old Tails version are present in the filesystem 1.446
And all persistent directories from the old Tails version have safe access rights 2.480
After features/support/hooks.rb:326 0.676
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:28.615
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.007
And no SquashFS delta is installed 0.175
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.291
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
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.483
When the network is plugged 0.078
And Tor is ready 17.998
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.412
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.041
Given I shutdown Tails and wait for the computer to power off 8.790
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.501
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.257
And the file system changes introduced in version 6.2~testoverlayfs are present 0.353
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.321
# 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.308
When the network is plugged 0.061
And Tor is ready 18.360
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.003
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.629
Given I shutdown Tails and wait for the computer to power off 7.076
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.024
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 1.885
And the file system changes introduced in version 6.3~testoverlayfs are present 0.477
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.338
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.255
When the network is plugged 0.071
And Tor is ready 18.966
Then the Upgrader considers the system as up-to-date 0.311
# 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 14.598
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.012
After features/support/hooks.rb:326 0.947
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
36.939
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 12.304
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.354
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.088
But a current signing key is available on our website 0.000
When the network is plugged 0.085
And Tor is ready 17.260
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.746
After features/support/hooks.rb:326 0.794
After features/support/hooks.rb:100 0.000