Project Number Date
test_Tails_ISO_devel 3554 19 Oct 2024, 12:16

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 18:19.473 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:59.401
Before features/support/hooks.rb:269 0.006
Given a computer 0.205
And I create a 7200 MiB disk named "old" 0.039
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 29.557
When I start Tails from USB drive "old" with network unplugged 1:24.680
Then the boot device has safe access rights 2.897
And Tails is running from USB drive "old" 0.334
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.290
And I unplug USB drive "old" 0.177
After features/support/hooks.rb:326 3.548
After features/support/hooks.rb:100 0.042
Tags: @product
2:4.404
Before features/support/hooks.rb:269 0.006
Given a computer 0.206
And I start Tails from USB drive "old" with network unplugged and I login 1:22.302
Then Tails is running from USB drive "old" 0.303
And I create a persistent partition 30.724
And I take note of which tps features are available 1.360
Then a Tails persistence partition exists on USB drive "old" 0.843
And I shutdown Tails and wait for the computer to power off 8.662
After features/support/hooks.rb:326 0.173
After features/support/hooks.rb:100 0.009
Tags: @product
2:56.010
Before features/support/hooks.rb:269 0.006
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.404
Then Tails is running from USB drive "old" 0.621
And all tps features are active 1.871
When I write some files expected to persist 1.625
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.207
And all persistence configuration files have safe access rights 0.382
And all persistent directories from the old Tails version have safe access rights 2.599
And I take note of which tps features are available 0.508
And I shutdown Tails and wait for the computer to power off 4.281
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.323
After features/support/hooks.rb:326 0.148
After features/support/hooks.rb:100 0.013
Tags: @product
2:24.852
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.912
And I log in to a new session 16.892
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.834
And I plug USB drive "to_upgrade" 2.373
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.948
Then the running Tails is installed on USB drive "to_upgrade" 18.503
And I unplug USB drive "to_upgrade" 0.194
And I unplug USB drive "__internal" 0.194
After features/support/hooks.rb:326 3.572
After features/support/hooks.rb:100 0.000
Tags: @product
2:9.724
Before features/support/hooks.rb:269 0.006
Given a computer 0.173
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:0.794
Then all tps features from the old Tails version are active 1.522
And Tails is running from USB drive "to_upgrade" 0.312
And the boot device has safe access rights 3.119
And the expected persistent files created with the old Tails version are present in the filesystem 1.447
And all persistent directories from the old Tails version have safe access rights 2.354
After features/support/hooks.rb:326 1.001
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:5.641
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 11.962
And no SquashFS delta is installed 0.159
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.271
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.076
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.344
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.511
When the network is plugged 0.061
And Tor is ready 21.418
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.283
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.682
Given I shutdown Tails and wait for the computer to power off 10.506
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.522
Then Tails is running version 6.2~testoverlayfs 0.022
And all tps features are active 2.071
And the file system changes introduced in version 6.2~testoverlayfs are present 0.283
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# 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.277
When the network is plugged 0.077
And Tor is ready 19.538
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.967
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.695
Given I shutdown Tails and wait for the computer to power off 4.253
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.148
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.001
And the file system changes introduced in version 6.3~testoverlayfs are present 0.463
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.318
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.256
When the network is plugged 0.073
And Tor is ready 20.671
Then the Upgrader considers the system as up-to-date 0.299
# 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 12.909
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.033
After features/support/hooks.rb:326 0.778
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
39.437
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 10.431
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.448
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.750
But a current signing key is available on our website 0.000
When the network is plugged 0.074
And Tor is ready 21.404
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.272
After features/support/hooks.rb:326 0.625
After features/support/hooks.rb:100 0.000