Project Number Date
test_Tails_ISO_stable 4937 12 Jul 2024, 12:35

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.531 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:27.487
Before features/support/hooks.rb:269 0.005
Given a computer 0.203
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 29.615
When I start Tails from USB drive "old" with network unplugged 1:52.582
Then the boot device has safe access rights 2.978
And Tails is running from USB drive "old" 0.325
And there is no persistence partition on USB drive "old" 0.088
And process "udev-watchdog" is running 0.112
And udev-watchdog is monitoring the correct device 0.287
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:326 3.541
After features/support/hooks.rb:100 0.040
Tags: @product
2:4.070
Before features/support/hooks.rb:269 0.006
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login 1:22.464
Then Tails is running from USB drive "old" 0.377
And I create a persistent partition 30.095
And I take note of which tps features are available 1.723
Then a Tails persistence partition exists on USB drive "old" 0.965
And I shutdown Tails and wait for the computer to power off 8.260
After features/support/hooks.rb:326 0.176
After features/support/hooks.rb:100 0.009
Tags: @product
2:47.650
Before features/support/hooks.rb:269 0.006
Given a computer 0.201
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.719
Then Tails is running from USB drive "old" 0.415
And all tps features are active 2.216
When I write some files expected to persist 1.967
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.279
And all persistence configuration files have safe access rights 0.393
And all persistent directories from the old Tails version have safe access rights 2.302
And I take note of which tps features are available 0.433
And I shutdown Tails and wait for the computer to power off 4.319
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.402
After features/support/hooks.rb:326 0.139
After features/support/hooks.rb:100 0.009
Tags: @product
2:27.204
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.642
And I log in to a new session 17.647
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.435
And I plug USB drive "to_upgrade" 2.376
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.444
Then the running Tails is installed on USB drive "to_upgrade" 19.153
And I unplug USB drive "to_upgrade" 0.285
And I unplug USB drive "__internal" 0.218
After features/support/hooks.rb:326 3.576
After features/support/hooks.rb:100 0.000
Tags: @product
2:7.403
Before features/support/hooks.rb:269 0.005
Given a computer 0.220
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:57.469
Then all tps features from the old Tails version are active 1.730
And Tails is running from USB drive "to_upgrade" 0.336
And the boot device has safe access rights 3.443
And the expected persistent files created with the old Tails version are present in the filesystem 1.659
And all persistent directories from the old Tails version have safe access rights 2.543
After features/support/hooks.rb:326 0.857
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:36.264
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 33.415
And no SquashFS delta is installed 0.099
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.345
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.301
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.476
When the network is plugged 0.045
And Tor is ready 20.013
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.693
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.361
Given I shutdown Tails and wait for the computer to power off 8.339
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.987
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.247
And the file system changes introduced in version 6.2~testoverlayfs are present 0.294
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.337
# 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.247
When the network is plugged 0.048
And Tor is ready 18.865
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.275
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.612
Given I shutdown Tails and wait for the computer to power off 4.549
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.009
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.154
And the file system changes introduced in version 6.3~testoverlayfs are present 0.500
And only the 6.3~testoverlayfs SquashFS delta is installed 0.078
# 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.324
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.324
When the network is plugged 0.056
And Tor is ready 19.385
Then the Upgrader considers the system as up-to-date 0.330
# 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.473
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.913
After features/support/hooks.rb:326 0.791
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
33.449
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.601
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.746
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the signing key used by the Upgrader is outdated 0.821
But a current signing key is available on our website 0.000
When the network is plugged 0.043
And Tor is ready 17.100
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.066
After features/support/hooks.rb:326 0.806
After features/support/hooks.rb:100 0.000