Project Number Date
test_Tails_ISO_stable 5320 07 Dec 2024, 12:31

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:32.370 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.835
Before features/support/hooks.rb:269 0.004
Given a computer 0.179
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 29.100
When I start Tails from USB drive "old" with network unplugged 1:44.390
Then the boot device has safe access rights 3.051
And Tails is running from USB drive "old" 0.344
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.109
And udev-watchdog is monitoring the correct device 0.301
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:326 7.987
After features/support/hooks.rb:100 0.008
Tags: @product
2:16.020
Before features/support/hooks.rb:269 0.005
Given a computer 0.308
And I start Tails from USB drive "old" with network unplugged and I login 1:30.440
Then Tails is running from USB drive "old" 0.436
And I create a persistent partition 34.139
And I take note of which tps features are available 1.451
Then a Tails persistence partition exists on USB drive "old" 0.879
And I shutdown Tails and wait for the computer to power off 8.363
After features/support/hooks.rb:326 0.174
After features/support/hooks.rb:100 0.008
Tags: @product
2:57.473
Before features/support/hooks.rb:269 0.005
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.946
Then Tails is running from USB drive "old" 0.349
And all tps features are active 1.847
When I write some files expected to persist 1.688
# 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.434
And all persistent directories from the old Tails version have safe access rights 3.667
And I take note of which tps features are available 0.478
And I shutdown Tails and wait for the computer to power off 4.333
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.318
After features/support/hooks.rb:326 0.126
After features/support/hooks.rb:100 0.007
Tags: @product
2:32.373
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.992
And I log in to a new session 20.474
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.664
And I plug USB drive "to_upgrade" 2.404
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.003
Then the running Tails is installed on USB drive "to_upgrade" 19.979
And I unplug USB drive "to_upgrade" 0.425
And I unplug USB drive "__internal" 0.427
After features/support/hooks.rb:326 2.178
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.272
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:10.197
Then all tps features from the old Tails version are active 1.673
And Tails is running from USB drive "to_upgrade" 0.306
And the boot device has safe access rights 3.268
And the expected persistent files created with the old Tails version are present in the filesystem 1.912
And all persistent directories from the old Tails version have safe access rights 2.727
After features/support/hooks.rb:326 0.602
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
6:30.896
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.336
And no SquashFS delta is installed 0.078
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.423
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.294
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.467
When the network is plugged 0.083
And Tor is ready 21.090
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.701
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.468
Given I shutdown Tails and wait for the computer to power off 8.677
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.203
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.308
And the file system changes introduced in version 6.2~testoverlayfs are present 0.318
And only the 6.2~testoverlayfs SquashFS delta is installed 0.100
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.361
# 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.283
When the network is plugged 0.074
And Tor is ready 18.692
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.872
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.207
Given I shutdown Tails and wait for the computer to power off 4.303
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.137
Then Tails is running version 6.3~testoverlayfs 0.027
And all tps features are active 2.020
And the file system changes introduced in version 6.3~testoverlayfs are present 0.519
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.298
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.370
When the network is plugged 0.078
And Tor is ready 20.946
Then the Upgrader considers the system as up-to-date 10.848
# 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.220
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.925
After features/support/hooks.rb:326 0.774
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
36.498
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.891
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.480
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.755
But a current signing key is available on our website 0.000
When the network is plugged 0.070
And Tor is ready 19.894
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.345
After features/support/hooks.rb:326 0.651
After features/support/hooks.rb:100 0.000