Project Number Date
test_Tails_ISO_stable 5122 27 Sep 2024, 08:43

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 20:1.005 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:9.562
Before features/support/hooks.rb:269 0.005
Given a computer 0.176
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 29.761
When I start Tails from USB drive "old" with network unplugged 1:34.557
Then the boot device has safe access rights 2.970
And Tails is running from USB drive "old" 0.320
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.089
And udev-watchdog is monitoring the correct device 0.331
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:326 3.722
After features/support/hooks.rb:100 0.009
Tags: @product
2:9.277
Before features/support/hooks.rb:269 0.005
Given a computer 0.223
And I start Tails from USB drive "old" with network unplugged and I login 1:28.226
Then Tails is running from USB drive "old" 0.368
And I create a persistent partition 31.406
And I take note of which tps features are available 1.937
Then a Tails persistence partition exists on USB drive "old" 0.782
And I shutdown Tails and wait for the computer to power off 6.330
After features/support/hooks.rb:326 0.184
After features/support/hooks.rb:100 0.009
Tags: @product
3:2.419
Before features/support/hooks.rb:269 0.005
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:24.806
Then Tails is running from USB drive "old" 0.400
And all tps features are active 2.336
When I write some files expected to persist 2.258
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.260
And all persistence configuration files have safe access rights 0.393
And all persistent directories from the old Tails version have safe access rights 2.618
And I take note of which tps features are available 0.535
And I shutdown Tails and wait for the computer to power off 4.171
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.450
After features/support/hooks.rb:326 0.118
After features/support/hooks.rb:100 0.009
Tags: @product
2:38.201
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.074
And I log in to a new session 19.015
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.959
And I plug USB drive "to_upgrade" 2.432
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.565
Then the running Tails is installed on USB drive "to_upgrade" 23.714
And I unplug USB drive "to_upgrade" 0.222
And I unplug USB drive "__internal" 0.217
After features/support/hooks.rb:326 2.746
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.934
Before features/support/hooks.rb:269 0.004
Given a computer 0.191
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.223
Then all tps features from the old Tails version are active 1.761
And Tails is running from USB drive "to_upgrade" 0.333
And the boot device has safe access rights 3.408
And the expected persistent files created with the old Tails version are present in the filesystem 1.489
And all persistent directories from the old Tails version have safe access rights 2.525
After features/support/hooks.rb:326 0.871
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
7:6.257
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 32.624
And no SquashFS delta is installed 0.159
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.401
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.084
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.292
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.681
When the network is plugged 0.093
And Tor is ready 22.446
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.149
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.935
Given I shutdown Tails and wait for the computer to power off 10.644
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.425
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.307
And the file system changes introduced in version 6.2~testoverlayfs are present 0.287
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.346
# 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.320
When the network is plugged 0.091
And Tor is ready 17.281
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.679
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.689
Given I shutdown Tails and wait for the computer to power off 4.306
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.216
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.130
And the file system changes introduced in version 6.3~testoverlayfs are present 0.474
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.322
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.340
When the network is plugged 0.069
And Tor is ready 48.374
Then the Upgrader considers the system as up-to-date 0.315
# 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.639
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.960
After features/support/hooks.rb:326 0.703
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
38.352
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 10.180
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.490
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the signing key used by the Upgrader is outdated 0.853
But a current signing key is available on our website 0.000
When the network is plugged 0.068
And Tor is ready 19.812
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.900
After features/support/hooks.rb:326 0.657
After features/support/hooks.rb:100 0.000