Project Number Date
test_Tails_ISO_devel 3510 10 Sep 2024, 12:50

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:47.345 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:45.626
Before features/support/hooks.rb:269 0.006
Given a computer 0.265
And I create a 7200 MiB disk named "old" 0.078
And I plug USB drive "old" 1.112
And I write an old version of the Tails USB image to disk "old" 56.314
When I start Tails from USB drive "old" with network unplugged 1:42.977
Then the boot device has safe access rights 3.545
And Tails is running from USB drive "old" 0.454
And there is no persistence partition on USB drive "old" 0.100
And process "udev-watchdog" is running 0.122
And udev-watchdog is monitoring the correct device 0.363
And I unplug USB drive "old" 0.291
After features/support/hooks.rb:326 3.520
After features/support/hooks.rb:100 0.023
Tags: @product
2:14.938
Before features/support/hooks.rb:269 0.007
Given a computer 0.261
And I start Tails from USB drive "old" with network unplugged and I login 1:27.974
Then Tails is running from USB drive "old" 0.393
And I create a persistent partition 34.678
And I take note of which tps features are available 2.048
Then a Tails persistence partition exists on USB drive "old" 0.857
And I shutdown Tails and wait for the computer to power off 8.725
After features/support/hooks.rb:326 0.186
After features/support/hooks.rb:100 0.011
Tags: @product
3:15.418
Before features/support/hooks.rb:269 0.008
Given a computer 0.312
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:32.757
Then Tails is running from USB drive "old" 0.463
And all tps features are active 2.872
When I write some files expected to persist 2.479
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.435
And all persistence configuration files have safe access rights 0.655
And all persistent directories from the old Tails version have safe access rights 3.439
And I take note of which tps features are available 0.686
And I shutdown Tails and wait for the computer to power off 4.521
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.794
After features/support/hooks.rb:326 0.121
After features/support/hooks.rb:100 0.010
Tags: @product
2:46.096
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 20.176
And I log in to a new session 24.039
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.905
And I plug USB drive "to_upgrade" 2.665
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.091
Then the running Tails is installed on USB drive "to_upgrade" 20.776
And I unplug USB drive "to_upgrade" 0.207
And I unplug USB drive "__internal" 0.233
After features/support/hooks.rb:326 3.748
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.340
Before features/support/hooks.rb:269 0.007
Given a computer 0.202
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.210
Then all tps features from the old Tails version are active 1.670
And Tails is running from USB drive "to_upgrade" 0.513
And the boot device has safe access rights 3.700
And the expected persistent files created with the old Tails version are present in the filesystem 1.545
And all persistent directories from the old Tails version have safe access rights 2.495
After features/support/hooks.rb:326 0.930
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:47.811
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 13.002
And no SquashFS delta is installed 0.115
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.457
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.082
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.305
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.557
When the network is plugged 0.092
And Tor is ready 19.646
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.680
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.204
Given I shutdown Tails and wait for the computer to power off 11.335
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.670
Then Tails is running version 6.2~testoverlayfs 0.022
And all tps features are active 2.347
And the file system changes introduced in version 6.2~testoverlayfs are present 0.389
And only the 6.2~testoverlayfs SquashFS delta is installed 0.076
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.396
# 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.341
When the network is plugged 0.073
And Tor is ready 17.660
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.298
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.603
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:5.728
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.397
And the file system changes introduced in version 6.3~testoverlayfs are present 0.569
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.420
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.278
When the network is plugged 0.084
And Tor is ready 19.163
Then the Upgrader considers the system as up-to-date 0.333
# 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.204
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.850
After features/support/hooks.rb:326 0.746
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
36.113
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.520
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.389
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.077
And the signing key used by the Upgrader is outdated 0.878
But a current signing key is available on our website 0.000
When the network is plugged 0.077
And Tor is ready 16.643
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.527
After features/support/hooks.rb:326 1.485
After features/support/hooks.rb:100 0.000