Project Number Date
test_Tails_ISO_devel 3400 26 May 2024, 13:22

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:17.499 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:8.221
Before features/support/hooks.rb:259 0.006
Given a computer 0.208
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 32.814
When I start Tails from USB drive "old" with network unplugged 1:30.197
Then the boot device has safe access rights 2.922
And Tails is running from USB drive "old" 0.319
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.312
And I unplug USB drive "old" 0.174
After features/support/hooks.rb:305 2.841
After features/support/hooks.rb:89 0.049
Tags: @product
2:16.026
Before features/support/hooks.rb:259 0.007
Given a computer 1.479
And I start Tails from USB drive "old" with network unplugged and I login 1:24.660
Then Tails is running from USB drive "old" 0.367
And I create a persistent partition 38.307
And I take note of which tps features are available 1.937
Then a Tails persistence partition exists on USB drive "old" 0.848
And I shutdown Tails and wait for the computer to power off 8.425
After features/support/hooks.rb:305 0.176
After features/support/hooks.rb:89 0.020
Tags: @product
2:51.130
Before features/support/hooks.rb:259 0.010
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.494
Then Tails is running from USB drive "old" 0.440
And all tps features are active 2.032
When I write some files expected to persist 1.888
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.365
And all persistence configuration files have safe access rights 0.428
And all persistent directories from the old Tails version have safe access rights 2.510
And I take note of which tps features are available 0.479
And I shutdown Tails and wait for the computer to power off 4.502
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.804
After features/support/hooks.rb:305 0.144
After features/support/hooks.rb:89 0.014
Tags: @product
2:34.979
Before features/support/hooks.rb:259 0.009
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.197
And I log in to a new session 19.735
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.395
And I plug USB drive "to_upgrade" 2.425
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.192
Then the running Tails is installed on USB drive "to_upgrade" 22.616
And I unplug USB drive "to_upgrade" 0.216
And I unplug USB drive "__internal" 0.199
After features/support/hooks.rb:305 3.595
After features/support/hooks.rb:89 0.000
Tags: @product
2:24.717
Before features/support/hooks.rb:259 0.009
Given a computer 0.198
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.963
Then all tps features from the old Tails version are active 1.731
And Tails is running from USB drive "to_upgrade" 0.309
And the boot device has safe access rights 3.407
And the expected persistent files created with the old Tails version are present in the filesystem 1.598
And all persistent directories from the old Tails version have safe access rights 2.506
After features/support/hooks.rb:305 0.554
After features/support/hooks.rb:89 0.009
Tags: @product @automatic_upgrade
6:24.430
Before features/support/hooks.rb:259 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 16.492
And no SquashFS delta is installed 0.163
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.325
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.139
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.336
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.439
When the network is plugged 0.036
And Tor is ready 24.624
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.902
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.523
Given I shutdown Tails and wait for the computer to power off 8.480
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.476
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.557
And the file system changes introduced in version 6.2~testoverlayfs are present 0.339
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.359
# 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.299
When the network is plugged 0.066
And Tor is ready 19.152
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.065
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.036
Given I shutdown Tails and wait for the computer to power off 4.363
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.444
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.205
And the file system changes introduced in version 6.3~testoverlayfs are present 0.502
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.336
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.315
When the network is plugged 0.046
And Tor is ready 18.533
Then the Upgrader considers the system as up-to-date 0.321
# 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.396
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.977
After features/support/hooks.rb:305 0.822
After features/support/hooks.rb:89 0.017
Tags: @product @automatic_upgrade
37.995
Before features/support/hooks.rb:259 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.315
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.387
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.483
But a current signing key is available on our website 0.000
When the network is plugged 0.034
And Tor is ready 19.654
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.048
After features/support/hooks.rb:305 0.730
After features/support/hooks.rb:89 0.000