Project Number Date
test_Tails_ISO_stable 5334 14 Dec 2024, 08:41

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 18:52.312 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:6.118
Before features/support/hooks.rb:269 0.005
Given a computer 0.188
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.060
And I write an old version of the Tails USB image to disk "old" 28.629
When I start Tails from USB drive "old" with network unplugged 1:32.189
Then the boot device has safe access rights 3.019
And Tails is running from USB drive "old" 0.333
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.278
And I unplug USB drive "old" 0.192
After features/support/hooks.rb:326 6.785
After features/support/hooks.rb:100 0.009
Tags: @product
2:8.183
Before features/support/hooks.rb:269 0.007
Given a computer 0.179
And I start Tails from USB drive "old" with network unplugged and I login 1:27.121
Then Tails is running from USB drive "old" 0.332
And I create a persistent partition 29.435
And I take note of which tps features are available 1.757
Then a Tails persistence partition exists on USB drive "old" 0.781
And I shutdown Tails and wait for the computer to power off 8.574
After features/support/hooks.rb:326 0.164
After features/support/hooks.rb:100 0.009
Tags: @product
2:54.436
Before features/support/hooks.rb:269 0.006
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.564
Then Tails is running from USB drive "old" 0.334
And all tps features are active 2.136
When I write some files expected to persist 5.001
# 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.423
And all persistent directories from the old Tails version have safe access rights 2.396
And I take note of which tps features are available 0.456
And I shutdown Tails and wait for the computer to power off 4.663
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.033
After features/support/hooks.rb:326 0.094
After features/support/hooks.rb:100 0.011
Tags: @product
2:35.558
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.024
And I log in to a new session 19.768
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.591
And I plug USB drive "to_upgrade" 2.466
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.964
Then the running Tails is installed on USB drive "to_upgrade" 26.320
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.217
After features/support/hooks.rb:326 4.017
After features/support/hooks.rb:100 0.000
Tags: @product
2:10.575
Before features/support/hooks.rb:269 0.005
Given a computer 0.186
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.584
Then all tps features from the old Tails version are active 1.524
And Tails is running from USB drive "to_upgrade" 0.299
And the boot device has safe access rights 3.106
And the expected persistent files created with the old Tails version are present in the filesystem 1.425
And all persistent directories from the old Tails version have safe access rights 2.447
After features/support/hooks.rb:326 0.672
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:21.348
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.450
And no SquashFS delta is installed 0.112
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.445
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.110
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.260
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.453
When the network is plugged 0.065
And Tor is ready 22.826
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.445
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.309
Given I shutdown Tails and wait for the computer to power off 8.372
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.411
Then Tails is running version 6.2~testoverlayfs 0.021
And all tps features are active 2.332
And the file system changes introduced in version 6.2~testoverlayfs are present 0.362
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.358
# 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.259
When the network is plugged 0.091
And Tor is ready 20.681
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.054
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.496
Given I shutdown Tails and wait for the computer to power off 4.340
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.109
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 1.982
And the file system changes introduced in version 6.3~testoverlayfs are present 0.484
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.295
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.282
When the network is plugged 0.085
And Tor is ready 18.046
Then the Upgrader considers the system as up-to-date 0.313
# 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.514
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.799
After features/support/hooks.rb:326 0.770
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
36.091
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 10.091
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.405
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 0.790
But a current signing key is available on our website 0.000
When the network is plugged 0.084
And Tor is ready 18.164
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.498
After features/support/hooks.rb:326 0.670
After features/support/hooks.rb:100 0.000