Project Number Date
test_Tails_ISO_devel 3502 04 Sep 2024, 12:49

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:28.501 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:57.846
Before features/support/hooks.rb:269 0.006
Given a computer 0.204
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 29.338
When I start Tails from USB drive "old" with network unplugged 1:23.289
Then the boot device has safe access rights 2.947
And Tails is running from USB drive "old" 0.332
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.275
And I unplug USB drive "old" 0.190
After features/support/hooks.rb:326 3.747
After features/support/hooks.rb:100 0.010
Tags: @product
2:12.624
Before features/support/hooks.rb:269 0.006
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login 1:30.002
Then Tails is running from USB drive "old" 0.329
And I create a persistent partition 31.306
And I take note of which tps features are available 1.454
Then a Tails persistence partition exists on USB drive "old" 0.756
And I shutdown Tails and wait for the computer to power off 8.593
After features/support/hooks.rb:326 0.152
After features/support/hooks.rb:100 0.010
Tags: @product
2:58.583
Before features/support/hooks.rb:269 0.007
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.240
Then Tails is running from USB drive "old" 0.373
And all tps features are active 1.990
When I write some files expected to persist 1.797
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.234
And all persistence configuration files have safe access rights 0.400
And all persistent directories from the old Tails version have safe access rights 2.262
And I take note of which tps features are available 0.373
And I shutdown Tails and wait for the computer to power off 4.634
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.076
After features/support/hooks.rb:326 0.139
After features/support/hooks.rb:100 0.010
Tags: @product
2:25.895
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 10.982
And I log in to a new session 18.280
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.972
And I plug USB drive "to_upgrade" 2.365
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.488
Then the running Tails is installed on USB drive "to_upgrade" 17.419
And I unplug USB drive "to_upgrade" 0.194
And I unplug USB drive "__internal" 0.191
After features/support/hooks.rb:326 3.510
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.573
Before features/support/hooks.rb:269 0.007
Given a computer 0.182
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.557
Then all tps features from the old Tails version are active 1.567
And Tails is running from USB drive "to_upgrade" 0.329
And the boot device has safe access rights 3.300
And the expected persistent files created with the old Tails version are present in the filesystem 1.370
And all persistent directories from the old Tails version have safe access rights 2.264
After features/support/hooks.rb:326 0.932
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:3.955
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 11.332
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.314
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.254
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.392
When the network is plugged 0.073
And Tor is ready 21.220
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.394
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.988
Given I shutdown Tails and wait for the computer to power off 8.461
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.664
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.049
And the file system changes introduced in version 6.2~testoverlayfs are present 0.325
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.293
# 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.301
When the network is plugged 0.082
And Tor is ready 15.364
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.474
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.198
Given I shutdown Tails and wait for the computer to power off 57.056
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:50.600
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.887
And the file system changes introduced in version 6.3~testoverlayfs are present 0.451
And only the 6.3~testoverlayfs SquashFS delta is installed 0.060
# 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.507
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.348
When the network is plugged 0.076
And Tor is ready 16.658
Then the Upgrader considers the system as up-to-date 10.787
# 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.221
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.878
After features/support/hooks.rb:326 0.812
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
33.022
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 9.593
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.298
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the signing key used by the Upgrader is outdated 0.783
But a current signing key is available on our website 0.000
When the network is plugged 0.064
And Tor is ready 15.730
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.489
After features/support/hooks.rb:326 0.933
After features/support/hooks.rb:100 0.000