Project Number Date
test_Tails_ISO_stable 4986 31 Jul 2024, 13:15

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 21:5.644 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:34.455
Before features/support/hooks.rb:269 0.007
Given a computer 1.478
And I create a 7200 MiB disk named "old" 0.664
And I plug USB drive "old" 1.153
And I write an old version of the Tails USB image to disk "old" 45.499
When I start Tails from USB drive "old" with network unplugged 1:40.753
Then the boot device has safe access rights 3.793
And Tails is running from USB drive "old" 0.389
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.110
And udev-watchdog is monitoring the correct device 0.340
And I unplug USB drive "old" 0.211
After features/support/hooks.rb:326 3.882
After features/support/hooks.rb:100 0.017
Tags: @product
2:27.474
Before features/support/hooks.rb:269 0.012
Given a computer 0.354
And I start Tails from USB drive "old" with network unplugged and I login 1:32.599
Then Tails is running from USB drive "old" 0.369
And I create a persistent partition 41.637
And I take note of which tps features are available 2.650
Then a Tails persistence partition exists on USB drive "old" 0.993
And I shutdown Tails and wait for the computer to power off 8.868
After features/support/hooks.rb:326 0.232
After features/support/hooks.rb:100 0.016
Tags: @product
3:3.571
Before features/support/hooks.rb:269 0.019
Given a computer 0.729
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.774
Then Tails is running from USB drive "old" 0.352
And all tps features are active 2.480
When I write some files expected to persist 2.060
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.299
And all persistence configuration files have safe access rights 0.439
And all persistent directories from the old Tails version have safe access rights 2.698
And I take note of which tps features are available 0.669
And I shutdown Tails and wait for the computer to power off 4.542
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.525
After features/support/hooks.rb:326 0.138
After features/support/hooks.rb:100 0.018
Tags: @product
3:0.825
Before features/support/hooks.rb:269 0.012
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 28.454
And I log in to a new session 19.934
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.518
And I plug USB drive "to_upgrade" 2.558
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:45.039
Then the running Tails is installed on USB drive "to_upgrade" 22.378
And I unplug USB drive "to_upgrade" 0.282
And I unplug USB drive "__internal" 0.658
After features/support/hooks.rb:326 1.864
After features/support/hooks.rb:100 0.000
Tags: @product
2:31.007
Before features/support/hooks.rb:269 0.010
Given a computer 0.386
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:20.294
Then all tps features from the old Tails version are active 2.223
And Tails is running from USB drive "to_upgrade" 0.411
And the boot device has safe access rights 3.468
And the expected persistent files created with the old Tails version are present in the filesystem 1.449
And all persistent directories from the old Tails version have safe access rights 2.773
After features/support/hooks.rb:326 1.043
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
6:51.274
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 26.722
And no SquashFS delta is installed 0.135
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.478
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.371
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.511
When the network is plugged 0.573
And Tor is ready 18.477
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.128
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.204
Given I shutdown Tails and wait for the computer to power off 9.035
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.177
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 2.734
And the file system changes introduced in version 6.2~testoverlayfs are present 0.355
And only the 6.2~testoverlayfs SquashFS delta is installed 0.102
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.382
# 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.291
When the network is plugged 0.056
And Tor is ready 18.768
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.453
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.227
Given I shutdown Tails and wait for the computer to power off 4.431
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.744
Then Tails is running version 6.3~testoverlayfs 0.031
And all tps features are active 2.289
And the file system changes introduced in version 6.3~testoverlayfs are present 0.594
And only the 6.3~testoverlayfs SquashFS delta is installed 0.089
# 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.411
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.458
When the network is plugged 0.054
And Tor is ready 17.846
Then the Upgrader considers the system as up-to-date 0.404
# 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.611
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.021
After features/support/hooks.rb:326 0.828
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
37.035
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.438
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.319
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.880
But a current signing key is available on our website 0.000
When the network is plugged 0.034
And Tor is ready 20.251
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.051
After features/support/hooks.rb:326 0.654
After features/support/hooks.rb:100 0.000