Project Number Date
test_Tails_ISO_stable 5268 15 Nov 2024, 16:05

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:56.950 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:22.355
Before features/support/hooks.rb:269 0.005
Given a computer 0.233
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 30.960
When I start Tails from USB drive "old" with network unplugged 1:45.341
Then the boot device has safe access rights 3.561
And Tails is running from USB drive "old" 0.378
And there is no persistence partition on USB drive "old" 0.082
And process "udev-watchdog" is running 0.115
And udev-watchdog is monitoring the correct device 0.348
And I unplug USB drive "old" 0.233
After features/support/hooks.rb:326 3.583
After features/support/hooks.rb:100 0.007
Tags: @product
2:16.193
Before features/support/hooks.rb:269 0.004
Given a computer 0.212
And I start Tails from USB drive "old" with network unplugged and I login 1:29.174
Then Tails is running from USB drive "old" 0.510
And I create a persistent partition 34.912
And I take note of which tps features are available 2.027
Then a Tails persistence partition exists on USB drive "old" 0.843
And I shutdown Tails and wait for the computer to power off 8.514
After features/support/hooks.rb:326 0.165
After features/support/hooks.rb:100 0.007
Tags: @product
3:5.014
Before features/support/hooks.rb:269 0.003
Given a computer 0.197
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.872
Then Tails is running from USB drive "old" 1.049
And all tps features are active 2.092
When I write some files expected to persist 2.756
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.234
And all persistence configuration files have safe access rights 0.380
And all persistent directories from the old Tails version have safe access rights 2.573
And I take note of which tps features are available 0.463
And I shutdown Tails and wait for the computer to power off 6.634
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.759
After features/support/hooks.rb:326 0.164
After features/support/hooks.rb:100 0.008
Tags: @product
2:37.487
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.542
And I log in to a new session 21.708
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.835
And I plug USB drive "to_upgrade" 2.573
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.457
Then the running Tails is installed on USB drive "to_upgrade" 22.916
And I unplug USB drive "to_upgrade" 0.214
And I unplug USB drive "__internal" 0.238
After features/support/hooks.rb:326 2.355
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.370
Before features/support/hooks.rb:269 0.006
Given a computer 0.247
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.257
Then all tps features from the old Tails version are active 1.752
And Tails is running from USB drive "to_upgrade" 0.343
And the boot device has safe access rights 3.916
And the expected persistent files created with the old Tails version are present in the filesystem 1.456
And all persistent directories from the old Tails version have safe access rights 2.397
After features/support/hooks.rb:326 0.870
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:5.434
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.283
And no SquashFS delta is installed 1.482
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.323
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.078
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.311
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.718
When the network is plugged 0.179
And Tor is ready 50.221
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.628
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.770
Given I shutdown Tails and wait for the computer to power off 11.564
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.509
Then Tails is running version 6.2~testoverlayfs 0.023
And all tps features are active 2.716
And the file system changes introduced in version 6.2~testoverlayfs are present 0.433
And only the 6.2~testoverlayfs SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.344
# 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.381
When the network is plugged 0.068
And Tor is ready 17.299
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.989
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.002
Given I shutdown Tails and wait for the computer to power off 4.399
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.332
Then Tails is running version 6.3~testoverlayfs 0.023
And all tps features are active 3.814
And the file system changes introduced in version 6.3~testoverlayfs are present 0.633
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.339
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.288
When the network is plugged 0.071
And Tor is ready 20.126
Then the Upgrader considers the system as up-to-date 0.347
# 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.381
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.192
After features/support/hooks.rb:326 0.875
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
1:8.092
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.921
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.671
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.880
But a current signing key is available on our website 0.000
When the network is plugged 0.277
And Tor is ready 50.689
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.585
After features/support/hooks.rb:326 0.734
After features/support/hooks.rb:100 0.000