Project Number Date
test_Tails_ISO_stable 5159 08 Oct 2024, 19:00

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:57.795 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:57.093
Before features/support/hooks.rb:269 0.006
Given a computer 0.250
And I create a 7200 MiB disk named "old" 0.082
And I plug USB drive "old" 1.070
And I write an old version of the Tails USB image to disk "old" 1:16.389
When I start Tails from USB drive "old" with network unplugged 1:34.671
Then the boot device has safe access rights 3.424
And Tails is running from USB drive "old" 0.437
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.110
And udev-watchdog is monitoring the correct device 0.392
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:326 3.535
After features/support/hooks.rb:100 0.010
Tags: @product
2:8.275
Before features/support/hooks.rb:269 0.005
Given a computer 0.325
And I start Tails from USB drive "old" with network unplugged and I login 1:23.637
Then Tails is running from USB drive "old" 0.411
And I create a persistent partition 33.020
And I take note of which tps features are available 1.337
Then a Tails persistence partition exists on USB drive "old" 0.948
And I shutdown Tails and wait for the computer to power off 8.594
After features/support/hooks.rb:326 0.233
After features/support/hooks.rb:100 0.011
Tags: @product
2:59.611
Before features/support/hooks.rb:269 0.006
Given a computer 0.212
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.900
Then Tails is running from USB drive "old" 0.768
And all tps features are active 3.821
When I write some files expected to persist 2.142
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.264
And all persistence configuration files have safe access rights 0.420
And all persistent directories from the old Tails version have safe access rights 2.733
And I take note of which tps features are available 0.489
And I shutdown Tails and wait for the computer to power off 4.384
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.473
After features/support/hooks.rb:326 0.152
After features/support/hooks.rb:100 0.008
Tags: @product
2:33.587
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.943
And I log in to a new session 19.408
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.913
And I plug USB drive "to_upgrade" 2.430
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.421
Then the running Tails is installed on USB drive "to_upgrade" 21.841
And I unplug USB drive "to_upgrade" 0.405
And I unplug USB drive "__internal" 0.222
After features/support/hooks.rb:326 2.528
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.433
Before features/support/hooks.rb:269 0.007
Given a computer 0.271
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.320
Then all tps features from the old Tails version are active 1.907
And Tails is running from USB drive "to_upgrade" 0.389
And the boot device has safe access rights 4.325
And the expected persistent files created with the old Tails version are present in the filesystem 2.114
And all persistent directories from the old Tails version have safe access rights 3.104
After features/support/hooks.rb:326 0.806
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
7:20.245
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 14.267
And no SquashFS delta is installed 0.133
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.360
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.083
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.422
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.473
When the network is plugged 0.102
And Tor is ready 19.511
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.336
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.831
Given I shutdown Tails and wait for the computer to power off 16.060
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:25.177
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.538
And the file system changes introduced in version 6.2~testoverlayfs are present 0.407
And only the 6.2~testoverlayfs SquashFS delta is installed 0.099
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.361
# 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.093
And Tor is ready 19.518
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.243
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.435
Given I shutdown Tails and wait for the computer to power off 4.360
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:19.080
Then Tails is running version 6.3~testoverlayfs 0.039
And all tps features are active 2.526
And the file system changes introduced in version 6.3~testoverlayfs are present 0.522
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.294
When the network is plugged 0.121
And Tor is ready 19.975
Then the Upgrader considers the system as up-to-date 0.344
# 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.715
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.000
After features/support/hooks.rb:326 0.818
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
37.548
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 10.485
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.442
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 0.809
But a current signing key is available on our website 0.000
When the network is plugged 0.075
And Tor is ready 19.786
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.892
After features/support/hooks.rb:326 0.714
After features/support/hooks.rb:100 0.000