Project Number Date
test_Tails_ISO_stable 5206 21 Oct 2024, 14:25

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 19:49.298 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:17.096
Before features/support/hooks.rb:269 0.004
Given a computer 0.199
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 32.942
When I start Tails from USB drive "old" with network unplugged 1:38.741
Then the boot device has safe access rights 3.048
And Tails is running from USB drive "old" 0.339
And there is no persistence partition on USB drive "old" 0.091
And process "udev-watchdog" is running 0.125
And udev-watchdog is monitoring the correct device 0.321
And I unplug USB drive "old" 0.190
After features/support/hooks.rb:326 3.518
After features/support/hooks.rb:100 0.023
Tags: @product
2:4.769
Before features/support/hooks.rb:269 0.006
Given a computer 0.575
And I start Tails from USB drive "old" with network unplugged and I login 1:22.408
Then Tails is running from USB drive "old" 0.335
And I create a persistent partition 32.805
And I take note of which tps features are available 1.467
Then a Tails persistence partition exists on USB drive "old" 0.817
And I shutdown Tails and wait for the computer to power off 6.359
After features/support/hooks.rb:326 0.177
After features/support/hooks.rb:100 0.009
Tags: @product
2:51.380
Before features/support/hooks.rb:269 0.006
Given a computer 0.244
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.830
Then Tails is running from USB drive "old" 1.369
And all tps features are active 2.096
When I write some files expected to persist 2.217
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.225
And all persistence configuration files have safe access rights 0.399
And all persistent directories from the old Tails version have safe access rights 2.581
And I take note of which tps features are available 0.431
And I shutdown Tails and wait for the computer to power off 4.183
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.798
After features/support/hooks.rb:326 0.126
After features/support/hooks.rb:100 0.009
Tags: @product
2:35.208
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.687
And I log in to a new session 18.883
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.461
And I plug USB drive "to_upgrade" 2.470
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.329
Then the running Tails is installed on USB drive "to_upgrade" 21.902
And I unplug USB drive "to_upgrade" 0.276
And I unplug USB drive "__internal" 0.196
After features/support/hooks.rb:326 2.570
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.408
Before features/support/hooks.rb:269 0.024
Given a computer 0.198
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.175
Then all tps features from the old Tails version are active 1.756
And Tails is running from USB drive "to_upgrade" 0.302
And the boot device has safe access rights 3.801
And the expected persistent files created with the old Tails version are present in the filesystem 1.659
And all persistent directories from the old Tails version have safe access rights 2.513
After features/support/hooks.rb:326 1.111
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:7.339
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 12.915
And no SquashFS delta is installed 0.094
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.347
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.312
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.441
When the network is plugged 0.081
And Tor is ready 18.069
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.689
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.844
Given I shutdown Tails and wait for the computer to power off 10.683
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:17.593
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.216
And the file system changes introduced in version 6.2~testoverlayfs are present 0.339
And only the 6.2~testoverlayfs SquashFS delta is installed 0.089
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.350
# 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.297
When the network is plugged 0.096
And Tor is ready 17.990
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.126
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.970
Given I shutdown Tails and wait for the computer to power off 4.349
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.725
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.198
And the file system changes introduced in version 6.3~testoverlayfs are present 0.507
And only the 6.3~testoverlayfs SquashFS delta is installed 0.093
# 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.357
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.376
When the network is plugged 0.073
And Tor is ready 45.569
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 13.937
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.193
After features/support/hooks.rb:326 0.763
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
33.095
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.045
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.409
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.083
And the signing key used by the Upgrader is outdated 0.752
But a current signing key is available on our website 0.000
When the network is plugged 0.098
And Tor is ready 14.771
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.935
After features/support/hooks.rb:326 0.637
After features/support/hooks.rb:100 0.000