Project Number Date
test_Tails_ISO_20522-ocr-more 52 03 Feb 2025, 16:47

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 21:36.840 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:54.693
Before features/support/hooks.rb:269 0.004
Given a computer 0.382
And I create a 7200 MiB disk named "old" 0.263
And I plug USB drive "old" 1.187
And I write an old version of the Tails USB image to disk "old" 53.656
When I start Tails from USB drive "old" with network unplugged 1:54.811
Then the boot device has safe access rights 3.357
And Tails is running from USB drive "old" 0.331
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.332
And I unplug USB drive "old" 0.207
After features/support/hooks.rb:326 7.311
After features/support/hooks.rb:100 0.008
Tags: @product
2:11.831
Before features/support/hooks.rb:269 0.005
Given a computer 0.314
And I start Tails from USB drive "old" with network unplugged and I login 1:24.522
Then Tails is running from USB drive "old" 0.323
And I create a persistent partition 34.840
And I take note of which tps features are available 1.899
Then a Tails persistence partition exists on USB drive "old" 0.930
And I shutdown Tails and wait for the computer to power off 9.001
After features/support/hooks.rb:326 0.201
After features/support/hooks.rb:100 0.013
Tags: @product
3:18.726
Before features/support/hooks.rb:269 0.014
Given a computer 0.266
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:28.262
Then Tails is running from USB drive "old" 0.346
And all tps features are active 8.011
When I write some files expected to persist 1.861
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.249
And all persistence configuration files have safe access rights 0.444
And all persistent directories from the old Tails version have safe access rights 2.679
And I take note of which tps features are available 3.124
And I shutdown Tails and wait for the computer to power off 6.404
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 27.076
After features/support/hooks.rb:326 0.219
After features/support/hooks.rb:100 0.013
Tags: @product
2:53.283
Before features/support/hooks.rb:269 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.947
And I log in to a new session 25.383
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.404
And I plug USB drive "to_upgrade" 2.585
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.442
Then the running Tails is installed on USB drive "to_upgrade" 27.985
And I unplug USB drive "to_upgrade" 0.239
And I unplug USB drive "__internal" 0.293
After features/support/hooks.rb:326 3.708
After features/support/hooks.rb:100 0.000
Tags: @product
2:23.915
Before features/support/hooks.rb:269 0.008
Given a computer 0.376
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.642
Then all tps features from the old Tails version are active 1.822
And Tails is running from USB drive "to_upgrade" 0.325
And the boot device has safe access rights 3.662
And the expected persistent files created with the old Tails version are present in the filesystem 1.526
And all persistent directories from the old Tails version have safe access rights 2.558
After features/support/hooks.rb:326 0.731
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:15.764
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 41.567
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.327
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.297
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.479
When the network is plugged 1.478
And Tor is ready 25.737
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.360
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.967
Given I shutdown Tails and wait for the computer to power off 10.958
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.499
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.314
And the file system changes introduced in version 6.2~testoverlayfs are present 0.319
And only the 6.2~testoverlayfs SquashFS delta is installed 0.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.316
# 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.330
When the network is plugged 0.073
And Tor is ready 16.291
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.996
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.499
Given I shutdown Tails and wait for the computer to power off 6.287
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.366
Then Tails is running version 6.3~testoverlayfs 0.021
And all tps features are active 2.175
And the file system changes introduced in version 6.3~testoverlayfs are present 0.496
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.294
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.304
When the network is plugged 0.088
And Tor is ready 18.838
Then the Upgrader considers the system as up-to-date 0.358
# 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.360
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.055
After features/support/hooks.rb:326 0.811
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
38.626
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.058
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.356
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the signing key used by the Upgrader is outdated 0.076
But a current signing key is available on our website 0.000
When the network is plugged 0.071
And Tor is ready 21.631
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.364
After features/support/hooks.rb:326 1.621
After features/support/hooks.rb:100 0.000