Project Number Date
test_Tails_ISO_stable 5212 23 Oct 2024, 08:56

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:12.458 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:19.126
Before features/support/hooks.rb:269 0.006
Given a computer 0.240
And I create a 7200 MiB disk named "old" 0.061
And I plug USB drive "old" 1.063
And I write an old version of the Tails USB image to disk "old" 30.998
When I start Tails from USB drive "old" with network unplugged 1:42.168
Then the boot device has safe access rights 3.484
And Tails is running from USB drive "old" 0.332
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.138
And udev-watchdog is monitoring the correct device 0.371
And I unplug USB drive "old" 0.192
After features/support/hooks.rb:326 7.708
After features/support/hooks.rb:100 0.010
Tags: @product
2:6.558
Before features/support/hooks.rb:269 0.007
Given a computer 0.218
And I start Tails from USB drive "old" with network unplugged and I login 1:22.975
Then Tails is running from USB drive "old" 0.371
And I create a persistent partition 32.049
And I take note of which tps features are available 1.457
Then a Tails persistence partition exists on USB drive "old" 0.933
And I shutdown Tails and wait for the computer to power off 8.551
After features/support/hooks.rb:326 0.230
After features/support/hooks.rb:100 0.008
Tags: @product
2:52.113
Before features/support/hooks.rb:269 0.005
Given a computer 0.240
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.441
Then Tails is running from USB drive "old" 0.966
And all tps features are active 2.360
When I write some files expected to persist 2.442
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.250
And all persistence configuration files have safe access rights 0.419
And all persistent directories from the old Tails version have safe access rights 3.303
And I take note of which tps features are available 0.589
And I shutdown Tails and wait for the computer to power off 6.419
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.680
After features/support/hooks.rb:326 0.147
After features/support/hooks.rb:100 0.009
Tags: @product
2:53.072
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 26.438
And I log in to a new session 21.839
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.929
And I plug USB drive "to_upgrade" 2.475
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.290
Then the running Tails is installed on USB drive "to_upgrade" 20.637
And I unplug USB drive "to_upgrade" 0.209
And I unplug USB drive "__internal" 0.251
After features/support/hooks.rb:326 3.518
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.136
Before features/support/hooks.rb:269 0.006
Given a computer 0.270
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.955
Then all tps features from the old Tails version are active 1.826
And Tails is running from USB drive "to_upgrade" 0.424
And the boot device has safe access rights 3.683
And the expected persistent files created with the old Tails version are present in the filesystem 1.514
And all persistent directories from the old Tails version have safe access rights 2.462
After features/support/hooks.rb:326 1.173
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:5.377
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 15.605
And no SquashFS delta is installed 0.578
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.951
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.284
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.473
When the network is plugged 0.073
And Tor is ready 23.364
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.929
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.077
Given I shutdown Tails and wait for the computer to power off 11.270
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.034
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.542
And the file system changes introduced in version 6.2~testoverlayfs are present 0.474
And only the 6.2~testoverlayfs SquashFS delta is installed 0.106
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.347
# 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.390
When the network is plugged 0.080
And Tor is ready 23.224
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.065
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.390
Given I shutdown Tails and wait for the computer to power off 4.343
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.509
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.534
And the file system changes introduced in version 6.3~testoverlayfs are present 0.455
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.397
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.323
When the network is plugged 0.072
And Tor is ready 17.421
Then the Upgrader considers the system as up-to-date 0.320
# 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.465
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.122
After features/support/hooks.rb:326 0.807
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
39.073
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 11.350
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.910
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.080
And the signing key used by the Upgrader is outdated 0.871
But a current signing key is available on our website 0.000
When the network is plugged 0.075
And Tor is ready 18.804
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.981
After features/support/hooks.rb:326 1.180
After features/support/hooks.rb:100 0.000