Project Number Date
test_Tails_ISO_devel 3410 01 Jun 2024, 12:44

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:44.348 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:15.065
Before features/support/hooks.rb:265 0.008
Given a computer 0.222
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 31.338
When I start Tails from USB drive "old" with network unplugged 1:38.141
Then the boot device has safe access rights 3.181
And Tails is running from USB drive "old" 0.397
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.109
And udev-watchdog is monitoring the correct device 0.309
And I unplug USB drive "old" 0.190
After features/support/hooks.rb:311 3.530
After features/support/hooks.rb:100 0.026
Tags: @product
2:19.123
Before features/support/hooks.rb:265 0.008
Given a computer 0.224
And I start Tails from USB drive "old" with network unplugged and I login 1:32.327
Then Tails is running from USB drive "old" 0.322
And I create a persistent partition 35.290
And I take note of which tps features are available 1.387
Then a Tails persistence partition exists on USB drive "old" 0.871
And I shutdown Tails and wait for the computer to power off 8.700
After features/support/hooks.rb:311 0.186
After features/support/hooks.rb:100 0.011
Tags: @product
2:45.888
Before features/support/hooks.rb:265 0.008
Given a computer 0.219
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:9.539
Then Tails is running from USB drive "old" 0.322
And all tps features are active 1.974
When I write some files expected to persist 1.674
# 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.374
And all persistent directories from the old Tails version have safe access rights 2.593
And I take note of which tps features are available 0.440
And I shutdown Tails and wait for the computer to power off 4.392
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.151
After features/support/hooks.rb:311 0.117
After features/support/hooks.rb:100 0.012
Tags: @product
2:25.158
Before features/support/hooks.rb:265 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 10.116
And I log in to a new session 18.875
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.261
And I plug USB drive "to_upgrade" 2.468
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.235
Then the running Tails is installed on USB drive "to_upgrade" 18.799
And I unplug USB drive "to_upgrade" 0.197
And I unplug USB drive "__internal" 0.205
After features/support/hooks.rb:311 3.263
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.767
Before features/support/hooks.rb:265 0.008
Given a computer 0.199
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.756
Then all tps features from the old Tails version are active 1.493
And Tails is running from USB drive "to_upgrade" 0.325
And the boot device has safe access rights 3.086
And the expected persistent files created with the old Tails version are present in the filesystem 1.540
And all persistent directories from the old Tails version have safe access rights 2.366
After features/support/hooks.rb:311 0.831
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
7:10.048
Before features/support/hooks.rb:265 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.809
And no SquashFS delta is installed 0.083
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.339
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.316
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.485
When the network is plugged 0.043
And Tor is ready 18.540
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.630
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.868
Given I shutdown Tails and wait for the computer to power off 8.559
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.322
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.161
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.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.431
# 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.258
When the network is plugged 0.040
And Tor is ready 18.159
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.312
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.984
Given I shutdown Tails and wait for the computer to power off 56.859
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.129
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.024
And the file system changes introduced in version 6.3~testoverlayfs are present 0.531
And only the 6.3~testoverlayfs SquashFS delta is installed 0.096
# 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.401
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.297
When the network is plugged 0.035
And Tor is ready 21.207
Then the Upgrader considers the system as up-to-date 0.322
# 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.190
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.155
After features/support/hooks.rb:311 0.822
After features/support/hooks.rb:100 0.039
Tags: @product @automatic_upgrade
36.296
Before features/support/hooks.rb:265 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.974
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.291
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 1.073
But a current signing key is available on our website 0.000
When the network is plugged 0.046
And Tor is ready 17.804
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.039
After features/support/hooks.rb:311 0.648
After features/support/hooks.rb:100 0.000