Project Number Date
test_Tails_ISO_stable 4971 24 Jul 2024, 22:31

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:7.144 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:39.943
Before features/support/hooks.rb:269 0.004
Given a computer 0.185
And I create a 7200 MiB disk named "old" 0.040
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 30.351
When I start Tails from USB drive "old" with network unplugged 2:4.105
Then the boot device has safe access rights 3.145
And Tails is running from USB drive "old" 0.328
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.332
And I unplug USB drive "old" 0.246
After features/support/hooks.rb:326 7.833
After features/support/hooks.rb:100 0.011
Tags: @product
2:10.153
Before features/support/hooks.rb:269 0.007
Given a computer 0.211
And I start Tails from USB drive "old" with network unplugged and I login 1:26.477
Then Tails is running from USB drive "old" 0.333
And I create a persistent partition 32.271
And I take note of which tps features are available 1.552
Then a Tails persistence partition exists on USB drive "old" 0.813
And I shutdown Tails and wait for the computer to power off 8.494
After features/support/hooks.rb:326 0.180
After features/support/hooks.rb:100 0.011
Tags: @product
2:48.488
Before features/support/hooks.rb:269 0.006
Given a computer 0.205
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.059
Then Tails is running from USB drive "old" 0.393
And all tps features are active 1.898
When I write some files expected to persist 1.752
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.221
And all persistence configuration files have safe access rights 0.526
And all persistent directories from the old Tails version have safe access rights 2.441
And I take note of which tps features are available 0.387
And I shutdown Tails and wait for the computer to power off 4.320
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.282
After features/support/hooks.rb:326 0.119
After features/support/hooks.rb:100 0.011
Tags: @product
2:27.966
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 10.401
And I log in to a new session 18.192
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.700
And I plug USB drive "to_upgrade" 2.451
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.091
Then the running Tails is installed on USB drive "to_upgrade" 20.711
And I unplug USB drive "to_upgrade" 0.210
And I unplug USB drive "__internal" 0.207
After features/support/hooks.rb:326 1.905
After features/support/hooks.rb:100 0.000
Tags: @product
2:7.945
Before features/support/hooks.rb:269 0.006
Given a computer 0.180
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:58.108
Then all tps features from the old Tails version are active 1.538
And Tails is running from USB drive "to_upgrade" 0.362
And the boot device has safe access rights 3.206
And the expected persistent files created with the old Tails version are present in the filesystem 1.524
And all persistent directories from the old Tails version have safe access rights 3.026
After features/support/hooks.rb:326 0.642
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:12.418
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 10.484
And no SquashFS delta is installed 0.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.359
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.076
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.374
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.478
When the network is plugged 0.049
And Tor is ready 21.751
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.657
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.880
Given I shutdown Tails and wait for the computer to power off 8.741
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.232
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.174
And the file system changes introduced in version 6.2~testoverlayfs are present 0.323
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# 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.326
When the network is plugged 0.039
And Tor is ready 20.105
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.621
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.524
Given I shutdown Tails and wait for the computer to power off 4.694
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.457
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.093
And the file system changes introduced in version 6.3~testoverlayfs are present 0.673
And only the 6.3~testoverlayfs SquashFS delta is installed 0.080
# 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.318
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.333
When the network is plugged 0.029
And Tor is ready 18.853
Then the Upgrader considers the system as up-to-date 0.386
# 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.540
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.171
After features/support/hooks.rb:326 0.769
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
40.229
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 13.604
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.305
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 0.879
But a current signing key is available on our website 0.000
When the network is plugged 0.052
And Tor is ready 18.422
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.898
After features/support/hooks.rb:326 0.757
After features/support/hooks.rb:100 0.000