Project Number Date
test_Tails_ISO_stable 5366 04 Jan 2025, 12:20

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:34.159 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:10.025
Before features/support/hooks.rb:269 0.004
Given a computer 0.175
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 29.140
When I start Tails from USB drive "old" with network unplugged 1:35.426
Then the boot device has safe access rights 3.177
And Tails is running from USB drive "old" 0.332
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.308
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:326 3.502
After features/support/hooks.rb:100 0.044
Tags: @product
2:10.510
Before features/support/hooks.rb:269 0.005
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login 1:23.284
Then Tails is running from USB drive "old" 0.316
And I create a persistent partition 35.719
And I take note of which tps features are available 1.448
Then a Tails persistence partition exists on USB drive "old" 0.801
And I shutdown Tails and wait for the computer to power off 8.760
After features/support/hooks.rb:326 0.140
After features/support/hooks.rb:100 0.010
Tags: @product
2:51.639
Before features/support/hooks.rb:269 0.005
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.733
Then Tails is running from USB drive "old" 0.340
And all tps features are active 1.937
When I write some files expected to persist 1.792
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.205
And all persistence configuration files have safe access rights 0.415
And all persistent directories from the old Tails version have safe access rights 2.305
And I take note of which tps features are available 0.428
And I shutdown Tails and wait for the computer to power off 4.337
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.960
After features/support/hooks.rb:326 0.087
After features/support/hooks.rb:100 0.009
Tags: @product
2:32.559
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.807
And I log in to a new session 19.117
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.921
And I plug USB drive "to_upgrade" 2.462
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.565
Then the running Tails is installed on USB drive "to_upgrade" 20.240
And I unplug USB drive "to_upgrade" 0.238
And I unplug USB drive "__internal" 0.206
After features/support/hooks.rb:326 3.038
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.485
Before features/support/hooks.rb:269 0.004
Given a computer 0.264
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.547
Then all tps features from the old Tails version are active 1.733
And Tails is running from USB drive "to_upgrade" 0.315
And the boot device has safe access rights 3.075
And the expected persistent files created with the old Tails version are present in the filesystem 1.420
And all persistent directories from the old Tails version have safe access rights 3.129
After features/support/hooks.rb:326 0.780
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:51.195
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 11.157
And no SquashFS delta is installed 0.168
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.424
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.293
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.453
When the network is plugged 0.072
And Tor is ready 21.302
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.132
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.441
Given I shutdown Tails and wait for the computer to power off 8.473
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.428
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.136
And the file system changes introduced in version 6.2~testoverlayfs are present 0.282
And only the 6.2~testoverlayfs SquashFS delta is installed 0.083
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.283
# 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.285
When the network is plugged 0.076
And Tor is ready 17.681
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.794
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.849
Given I shutdown Tails and wait for the computer to power off 4.258
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.690
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.156
And the file system changes introduced in version 6.3~testoverlayfs are present 0.499
And only the 6.3~testoverlayfs SquashFS delta is installed 0.060
# 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.329
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.466
When the network is plugged 0.093
And Tor is ready 47.994
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 14.474
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.950
After features/support/hooks.rb:326 0.762
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
36.744
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 10.141
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.459
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.068
But a current signing key is available on our website 0.000
When the network is plugged 0.083
And Tor is ready 19.561
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.368
After features/support/hooks.rb:326 0.661
After features/support/hooks.rb:100 0.000