Project Number Date
test_Tails_ISO_devel 3424 11 Jun 2024, 12:26

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 18:42.811 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
1:54.802
Before features/support/hooks.rb:269 0.007
Given a computer 0.227
And I create a 7200 MiB disk named "old" 0.039
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 29.928
When I start Tails from USB drive "old" with network unplugged 1:19.835
Then the boot device has safe access rights 2.799
And Tails is running from USB drive "old" 0.324
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.089
And udev-watchdog is monitoring the correct device 0.280
And I unplug USB drive "old" 0.171
After features/support/hooks.rb:315 3.579
After features/support/hooks.rb:100 0.011
Tags: @product
2:6.664
Before features/support/hooks.rb:269 0.007
Given a computer 0.210
And I start Tails from USB drive "old" with network unplugged and I login 1:22.053
Then Tails is running from USB drive "old" 0.310
And I create a persistent partition 33.493
And I take note of which tps features are available 1.416
Then a Tails persistence partition exists on USB drive "old" 0.824
And I shutdown Tails and wait for the computer to power off 8.354
After features/support/hooks.rb:315 0.184
After features/support/hooks.rb:100 0.011
Tags: @product
2:53.681
Before features/support/hooks.rb:269 0.007
Given a computer 0.251
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.206
Then Tails is running from USB drive "old" 0.396
And all tps features are active 1.891
When I write some files expected to persist 1.715
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.303
And all persistence configuration files have safe access rights 0.446
And all persistent directories from the old Tails version have safe access rights 2.467
And I take note of which tps features are available 0.386
And I shutdown Tails and wait for the computer to power off 4.320
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.296
After features/support/hooks.rb:315 0.134
After features/support/hooks.rb:100 0.030
Tags: @product
2:23.274
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.013
And I log in to a new session 19.133
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.519
And I plug USB drive "to_upgrade" 2.446
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.833
Then the running Tails is installed on USB drive "to_upgrade" 15.918
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.202
After features/support/hooks.rb:315 2.825
After features/support/hooks.rb:100 0.000
Tags: @product
2:10.003
Before features/support/hooks.rb:269 0.008
Given a computer 0.236
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:0.947
Then all tps features from the old Tails version are active 1.468
And Tails is running from USB drive "to_upgrade" 0.307
And the boot device has safe access rights 3.282
And the expected persistent files created with the old Tails version are present in the filesystem 1.396
And all persistent directories from the old Tails version have safe access rights 2.363
After features/support/hooks.rb:315 0.680
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:38.180
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 10.751
And no SquashFS delta is installed 0.073
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.305
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.122
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.298
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.436
When the network is plugged 0.042
And Tor is ready 22.106
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.033
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.345
Given I shutdown Tails and wait for the computer to power off 8.588
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.282
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.133
And the file system changes introduced in version 6.2~testoverlayfs are present 0.361
And only the 6.2~testoverlayfs SquashFS delta is installed 0.058
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.315
# 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.248
When the network is plugged 0.037
And Tor is ready 18.251
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.229
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.734
Given I shutdown Tails and wait for the computer to power off 4.348
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.914
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.001
And the file system changes introduced in version 6.3~testoverlayfs are present 0.478
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.338
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.290
When the network is plugged 0.038
And Tor is ready 16.912
Then the Upgrader considers the system as up-to-date 10.784
# 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.383
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.832
After features/support/hooks.rb:315 0.679
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
36.205
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.025
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.360
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.084
And the signing key used by the Upgrader is outdated 0.948
But a current signing key is available on our website 0.000
When the network is plugged 0.044
And Tor is ready 18.241
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.498
After features/support/hooks.rb:315 0.809
After features/support/hooks.rb:100 0.000