Project Number Date
test_Tails_ISO_devel 3398 24 May 2024, 13:17

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:38.132 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:16.264
Before features/support/hooks.rb:259 0.008
Given a computer 0.206
And I create a 7200 MiB disk named "old" 0.079
And I plug USB drive "old" 1.073
And I write an old version of the Tails USB image to disk "old" 31.842
When I start Tails from USB drive "old" with network unplugged 1:37.773
Then the boot device has safe access rights 4.119
And Tails is running from USB drive "old" 0.449
And there is no persistence partition on USB drive "old" 0.095
And process "udev-watchdog" is running 0.105
And udev-watchdog is monitoring the correct device 0.324
And I unplug USB drive "old" 0.195
After features/support/hooks.rb:305 7.228
After features/support/hooks.rb:89 0.009
Tags: @product
2:12.389
Before features/support/hooks.rb:259 0.006
Given a computer 0.272
And I start Tails from USB drive "old" with network unplugged and I login 1:25.104
Then Tails is running from USB drive "old" 0.386
And I create a persistent partition 35.791
And I take note of which tps features are available 1.374
Then a Tails persistence partition exists on USB drive "old" 0.746
And I shutdown Tails and wait for the computer to power off 8.713
After features/support/hooks.rb:305 0.248
After features/support/hooks.rb:89 0.013
Tags: @product
3:1.803
Before features/support/hooks.rb:259 0.009
Given a computer 0.233
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.087
Then Tails is running from USB drive "old" 0.471
And all tps features are active 2.643
When I write some files expected to persist 2.145
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.493
And all persistence configuration files have safe access rights 0.587
And all persistent directories from the old Tails version have safe access rights 2.543
And I take note of which tps features are available 0.537
And I shutdown Tails and wait for the computer to power off 4.210
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.851
After features/support/hooks.rb:305 0.143
After features/support/hooks.rb:89 0.011
Tags: @product
2:37.006
Before features/support/hooks.rb:259 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 12.192
And I log in to a new session 19.858
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.422
And I plug USB drive "to_upgrade" 3.591
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.097
Then the running Tails is installed on USB drive "to_upgrade" 23.380
And I unplug USB drive "to_upgrade" 0.243
And I unplug USB drive "__internal" 0.220
After features/support/hooks.rb:305 2.077
After features/support/hooks.rb:89 0.000
Tags: @product
2:18.129
Before features/support/hooks.rb:259 0.007
Given a computer 0.222
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.521
Then all tps features from the old Tails version are active 1.647
And Tails is running from USB drive "to_upgrade" 0.333
And the boot device has safe access rights 3.387
And the expected persistent files created with the old Tails version are present in the filesystem 1.516
And all persistent directories from the old Tails version have safe access rights 2.499
After features/support/hooks.rb:305 0.663
After features/support/hooks.rb:89 0.013
Tags: @product @automatic_upgrade
6:37.143
Before features/support/hooks.rb:259 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.071
And no SquashFS delta is installed 0.172
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.321
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.277
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.471
When the network is plugged 0.037
And Tor is ready 26.569
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.085
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.843
Given I shutdown Tails and wait for the computer to power off 11.104
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.001
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.545
And the file system changes introduced in version 6.2~testoverlayfs are present 0.413
And only the 6.2~testoverlayfs SquashFS delta is installed 0.099
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.357
# 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.353
When the network is plugged 0.434
And Tor is ready 18.964
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.228
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.155
Given I shutdown Tails and wait for the computer to power off 4.460
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.669
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.983
And the file system changes introduced in version 6.3~testoverlayfs are present 0.482
And only the 6.3~testoverlayfs SquashFS delta is installed 0.061
# 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.341
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.265
When the network is plugged 0.035
And Tor is ready 20.205
Then the Upgrader considers the system as up-to-date 0.323
# 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 13.675
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.040
After features/support/hooks.rb:305 0.873
After features/support/hooks.rb:89 0.020
Tags: @product @automatic_upgrade
35.395
Before features/support/hooks.rb:259 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.640
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.333
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.486
But a current signing key is available on our website 0.000
When the network is plugged 0.036
And Tor is ready 17.594
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.245
After features/support/hooks.rb:305 0.968
After features/support/hooks.rb:89 0.000