Project Number Date
test_Tails_ISO_stable 5357 26 Dec 2024, 12:15

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:3.792 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:7.182
Before features/support/hooks.rb:269 0.005
Given a computer 0.183
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 30.089
When I start Tails from USB drive "old" with network unplugged 1:31.833
Then the boot device has safe access rights 2.979
And Tails is running from USB drive "old" 0.322
And there is no persistence partition on USB drive "old" 0.085
And process "udev-watchdog" is running 0.106
And udev-watchdog is monitoring the correct device 0.303
And I unplug USB drive "old" 0.180
After features/support/hooks.rb:326 1.065
After features/support/hooks.rb:100 0.007
Tags: @product
2:11.494
Before features/support/hooks.rb:269 0.005
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login 1:28.291
Then Tails is running from USB drive "old" 0.332
And I create a persistent partition 32.069
And I take note of which tps features are available 1.476
Then a Tails persistence partition exists on USB drive "old" 0.865
And I shutdown Tails and wait for the computer to power off 8.269
After features/support/hooks.rb:326 0.205
After features/support/hooks.rb:100 0.009
Tags: @product
3:0.300
Before features/support/hooks.rb:269 0.006
Given a computer 0.214
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:24.399
Then Tails is running from USB drive "old" 0.344
And all tps features are active 1.912
When I write some files expected to persist 1.788
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.243
And all persistence configuration files have safe access rights 0.381
And all persistent directories from the old Tails version have safe access rights 2.375
And I take note of which tps features are available 0.435
And I shutdown Tails and wait for the computer to power off 4.190
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.014
After features/support/hooks.rb:326 0.104
After features/support/hooks.rb:100 0.008
Tags: @product
2:33.003
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 11.431
And I log in to a new session 19.544
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.587
And I plug USB drive "to_upgrade" 2.372
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.371
Then the running Tails is installed on USB drive "to_upgrade" 23.265
And I unplug USB drive "to_upgrade" 0.207
And I unplug USB drive "__internal" 0.223
After features/support/hooks.rb:326 2.170
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.213
Before features/support/hooks.rb:269 0.007
Given a computer 0.241
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.947
Then all tps features from the old Tails version are active 1.466
And Tails is running from USB drive "to_upgrade" 0.448
And the boot device has safe access rights 3.448
And the expected persistent files created with the old Tails version are present in the filesystem 1.372
And all persistent directories from the old Tails version have safe access rights 2.288
After features/support/hooks.rb:326 1.091
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:26.941
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 11.877
And no SquashFS delta is installed 0.342
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.629
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.091
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.335
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.502
When the network is plugged 0.198
And Tor is ready 18.583
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.794
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.120
Given I shutdown Tails and wait for the computer to power off 10.642
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.752
Then Tails is running version 6.2~testoverlayfs 0.023
And all tps features are active 2.063
And the file system changes introduced in version 6.2~testoverlayfs are present 0.306
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.307
# 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.280
When the network is plugged 0.077
And Tor is ready 16.824
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.603
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.014
Given I shutdown Tails and wait for the computer to power off 4.173
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:50.043
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 3.541
And the file system changes introduced in version 6.3~testoverlayfs are present 0.440
And only the 6.3~testoverlayfs SquashFS delta is installed 0.083
# 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.263
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.284
When the network is plugged 0.088
And Tor is ready 19.160
Then the Upgrader considers the system as up-to-date 10.933
# 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.554
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.917
After features/support/hooks.rb:326 0.739
After features/support/hooks.rb:100 0.055
Tags: @product @automatic_upgrade
32.655
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.143
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.408
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.061
But a current signing key is available on our website 0.000
When the network is plugged 0.062
And Tor is ready 15.615
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.304
After features/support/hooks.rb:326 1.100
After features/support/hooks.rb:100 0.000