Project Number Date
test_Tails_ISO_stable 5058 30 Aug 2024, 08:32

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:29.987 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.991
Before features/support/hooks.rb:269 0.004
Given a computer 0.183
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 30.597
When I start Tails from USB drive "old" with network unplugged 1:42.007
Then the boot device has safe access rights 3.099
And Tails is running from USB drive "old" 0.303
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.305
And I unplug USB drive "old" 0.230
After features/support/hooks.rb:326 3.599
After features/support/hooks.rb:100 0.009
Tags: @product
2:7.064
Before features/support/hooks.rb:269 0.005
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login 1:23.581
Then Tails is running from USB drive "old" 0.359
And I create a persistent partition 31.506
And I take note of which tps features are available 1.909
Then a Tails persistence partition exists on USB drive "old" 0.837
And I shutdown Tails and wait for the computer to power off 8.665
After features/support/hooks.rb:326 0.244
After features/support/hooks.rb:100 0.016
Tags: @product
2:55.088
Before features/support/hooks.rb:269 0.008
Given a computer 0.244
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.218
Then Tails is running from USB drive "old" 0.416
And all tps features are active 2.112
When I write some files expected to persist 1.777
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.215
And all persistence configuration files have safe access rights 0.384
And all persistent directories from the old Tails version have safe access rights 2.620
And I take note of which tps features are available 0.449
And I shutdown Tails and wait for the computer to power off 4.490
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.159
After features/support/hooks.rb:326 0.129
After features/support/hooks.rb:100 0.010
Tags: @product
2:33.665
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.838
And I log in to a new session 22.083
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.446
And I plug USB drive "to_upgrade" 2.482
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.485
Then the running Tails is installed on USB drive "to_upgrade" 20.925
And I unplug USB drive "to_upgrade" 0.201
And I unplug USB drive "__internal" 0.202
After features/support/hooks.rb:326 2.539
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.959
Before features/support/hooks.rb:269 0.009
Given a computer 0.198
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.230
Then all tps features from the old Tails version are active 1.664
And Tails is running from USB drive "to_upgrade" 0.343
And the boot device has safe access rights 3.417
And the expected persistent files created with the old Tails version are present in the filesystem 1.482
And all persistent directories from the old Tails version have safe access rights 2.622
After features/support/hooks.rb:326 0.848
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:41.870
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 12.583
And no SquashFS delta is installed 0.328
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.303
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.290
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.521
When the network is plugged 0.077
And Tor is ready 19.443
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.802
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.102
Given I shutdown Tails and wait for the computer to power off 8.840
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.847
Then Tails is running version 6.2~testoverlayfs 0.057
And all tps features are active 6.758
And the file system changes introduced in version 6.2~testoverlayfs are present 0.316
And only the 6.2~testoverlayfs SquashFS delta is installed 0.082
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.332
# 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.283
When the network is plugged 0.268
And Tor is ready 14.900
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.821
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.049
Given I shutdown Tails and wait for the computer to power off 4.507
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.266
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.274
And the file system changes introduced in version 6.3~testoverlayfs are present 0.467
And only the 6.3~testoverlayfs SquashFS delta is installed 0.087
# 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.309
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.287
When the network is plugged 0.083
And Tor is ready 17.016
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 15.086
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.037
After features/support/hooks.rb:326 0.811
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
36.347
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 11.861
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.729
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.799
But a current signing key is available on our website 0.000
When the network is plugged 0.114
And Tor is ready 15.912
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.871
After features/support/hooks.rb:326 1.040
After features/support/hooks.rb:100 0.000