Project Number Date
test_Tails_ISO_20522-ocr-more 24 02 Jan 2025, 05:05

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:59.017 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:4.870
Before features/support/hooks.rb:269 0.005
Given a computer 0.216
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 29.469
When I start Tails from USB drive "old" with network unplugged 1:29.656
Then the boot device has safe access rights 3.395
And Tails is running from USB drive "old" 0.348
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.337
And I unplug USB drive "old" 0.191
After features/support/hooks.rb:326 3.560
After features/support/hooks.rb:100 0.070
Tags: @product
2:7.481
Before features/support/hooks.rb:269 0.005
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login 1:23.816
Then Tails is running from USB drive "old" 0.350
And I create a persistent partition 32.267
And I take note of which tps features are available 1.802
Then a Tails persistence partition exists on USB drive "old" 0.772
And I shutdown Tails and wait for the computer to power off 8.283
After features/support/hooks.rb:326 0.197
After features/support/hooks.rb:100 0.008
Tags: @product
2:59.004
Before features/support/hooks.rb:269 0.005
Given a computer 0.206
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.209
Then Tails is running from USB drive "old" 0.343
And all tps features are active 2.365
When I write some files expected to persist 1.611
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.225
And all persistence configuration files have safe access rights 0.379
And all persistent directories from the old Tails version have safe access rights 2.439
And I take note of which tps features are available 0.484
And I shutdown Tails and wait for the computer to power off 4.293
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.446
After features/support/hooks.rb:326 0.178
After features/support/hooks.rb:100 0.012
Tags: @product
2:38.221
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.953
And I log in to a new session 23.357
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.937
And I plug USB drive "to_upgrade" 2.780
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.124
Then the running Tails is installed on USB drive "to_upgrade" 23.593
And I unplug USB drive "to_upgrade" 0.215
And I unplug USB drive "__internal" 0.258
After features/support/hooks.rb:326 7.549
After features/support/hooks.rb:100 0.000
Tags: @product
2:4.555
Before features/support/hooks.rb:269 0.007
Given a computer 0.195
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:55.012
Then all tps features from the old Tails version are active 1.725
And Tails is running from USB drive "to_upgrade" 0.494
And the boot device has safe access rights 3.314
And the expected persistent files created with the old Tails version are present in the filesystem 1.417
And all persistent directories from the old Tails version have safe access rights 2.394
After features/support/hooks.rb:326 0.679
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:14.794
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 29.163
And no SquashFS delta is installed 0.117
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.589
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.106
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.330
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.468
When the network is plugged 0.065
And Tor is ready 49.916
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.598
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.562
Given I shutdown Tails and wait for the computer to power off 11.425
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.657
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.460
And the file system changes introduced in version 6.2~testoverlayfs are present 0.304
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.313
# 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.294
When the network is plugged 0.085
And Tor is ready 17.719
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.138
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.070
Given I shutdown Tails and wait for the computer to power off 4.327
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.728
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.267
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.125
# 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.450
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.388
When the network is plugged 0.077
And Tor is ready 19.677
Then the Upgrader considers the system as up-to-date 0.313
# 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.182
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.267
After features/support/hooks.rb:326 1.437
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
50.088
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 24.512
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.323
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the signing key used by the Upgrader is outdated 0.253
But a current signing key is available on our website 0.000
When the network is plugged 0.092
And Tor is ready 19.807
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.033
After features/support/hooks.rb:326 1.164
After features/support/hooks.rb:100 0.000