Project Number Date
test_Tails_ISO_devel 3615 18 Dec 2024, 12:53

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:56.296 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:55.362
Before features/support/hooks.rb:269 0.004
Given a computer 0.234
And I create a 7200 MiB disk named "old" 0.069
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 1:16.869
When I start Tails from USB drive "old" with network unplugged 1:33.004
Then the boot device has safe access rights 3.160
And Tails is running from USB drive "old" 0.312
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.315
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:326 6.715
After features/support/hooks.rb:100 0.009
Tags: @product
2:13.887
Before features/support/hooks.rb:269 0.005
Given a computer 0.269
And I start Tails from USB drive "old" with network unplugged and I login 1:27.549
Then Tails is running from USB drive "old" 0.343
And I create a persistent partition 34.959
And I take note of which tps features are available 1.502
Then a Tails persistence partition exists on USB drive "old" 0.851
And I shutdown Tails and wait for the computer to power off 8.409
After features/support/hooks.rb:326 0.182
After features/support/hooks.rb:100 0.010
Tags: @product
2:47.440
Before features/support/hooks.rb:269 0.006
Given a computer 0.213
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.030
Then Tails is running from USB drive "old" 0.880
And all tps features are active 2.261
When I write some files expected to persist 1.592
# 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.408
And all persistent directories from the old Tails version have safe access rights 3.073
And I take note of which tps features are available 0.434
And I shutdown Tails and wait for the computer to power off 4.310
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.029
After features/support/hooks.rb:326 0.154
After features/support/hooks.rb:100 0.010
Tags: @product
2:33.949
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 11.394
And I log in to a new session 19.862
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.429
And I plug USB drive "to_upgrade" 2.358
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.048
Then the running Tails is installed on USB drive "to_upgrade" 23.394
And I unplug USB drive "to_upgrade" 0.207
And I unplug USB drive "__internal" 0.254
After features/support/hooks.rb:326 2.033
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.219
Before features/support/hooks.rb:269 0.006
Given a computer 0.197
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.828
Then all tps features from the old Tails version are active 1.562
And Tails is running from USB drive "to_upgrade" 0.296
And the boot device has safe access rights 3.253
And the expected persistent files created with the old Tails version are present in the filesystem 1.739
And all persistent directories from the old Tails version have safe access rights 2.340
After features/support/hooks.rb:326 0.619
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:34.438
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 13.776
And no SquashFS delta is installed 0.120
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.302
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.469
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.447
When the network is plugged 0.079
And Tor is ready 22.353
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.918
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.967
Given I shutdown Tails and wait for the computer to power off 10.528
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.007
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.258
And the file system changes introduced in version 6.2~testoverlayfs are present 0.308
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.287
# 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.265
When the network is plugged 0.069
And Tor is ready 19.065
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.315
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.066
Given I shutdown Tails and wait for the computer to power off 4.629
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.808
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.954
And the file system changes introduced in version 6.3~testoverlayfs are present 0.493
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.427
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.268
When the network is plugged 0.066
And Tor is ready 18.188
Then the Upgrader considers the system as up-to-date 10.797
# 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.066
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.894
After features/support/hooks.rb:326 0.773
After features/support/hooks.rb:100 0.027
Tags: @product @automatic_upgrade
38.999
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.023
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.016
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 0.823
But a current signing key is available on our website 0.000
When the network is plugged 0.084
And Tor is ready 19.597
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.389
After features/support/hooks.rb:326 0.652
After features/support/hooks.rb:100 0.000