Project Number Date
test_Tails_ISO_devel 3512 10 Sep 2024, 16:14

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:53.976 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:14.510
Before features/support/hooks.rb:269 0.007
Given a computer 0.234
And I create a 7200 MiB disk named "old" 0.059
And I plug USB drive "old" 1.075
And I write an old version of the Tails USB image to disk "old" 29.737
When I start Tails from USB drive "old" with network unplugged 1:39.027
Then the boot device has safe access rights 3.255
And Tails is running from USB drive "old" 0.420
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.089
And udev-watchdog is monitoring the correct device 0.344
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:326 0.829
After features/support/hooks.rb:100 0.010
Tags: @product
2:9.129
Before features/support/hooks.rb:269 0.006
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login 1:25.219
Then Tails is running from USB drive "old" 0.376
And I create a persistent partition 31.979
And I take note of which tps features are available 1.631
Then a Tails persistence partition exists on USB drive "old" 0.852
And I shutdown Tails and wait for the computer to power off 8.870
After features/support/hooks.rb:326 0.188
After features/support/hooks.rb:100 0.010
Tags: @product
3:16.393
Before features/support/hooks.rb:269 0.007
Given a computer 0.224
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:37.201
Then Tails is running from USB drive "old" 0.351
And all tps features are active 1.934
When I write some files expected to persist 1.827
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.260
And all persistence configuration files have safe access rights 0.562
And all persistent directories from the old Tails version have safe access rights 2.914
And I take note of which tps features are available 0.581
And I shutdown Tails and wait for the computer to power off 4.465
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.069
After features/support/hooks.rb:326 0.203
After features/support/hooks.rb:100 0.008
Tags: @product
2:41.083
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.463
And I log in to a new session 25.173
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.638
And I plug USB drive "to_upgrade" 2.476
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.514
Then the running Tails is installed on USB drive "to_upgrade" 19.409
And I unplug USB drive "to_upgrade" 0.199
And I unplug USB drive "__internal" 0.208
After features/support/hooks.rb:326 7.499
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.410
Before features/support/hooks.rb:269 0.010
Given a computer 0.374
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.096
Then all tps features from the old Tails version are active 1.710
And Tails is running from USB drive "to_upgrade" 0.325
And the boot device has safe access rights 3.587
And the expected persistent files created with the old Tails version are present in the filesystem 1.493
And all persistent directories from the old Tails version have safe access rights 2.821
After features/support/hooks.rb:326 0.639
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:33.061
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 14.191
And no SquashFS delta is installed 0.092
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.417
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.309
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.485
When the network is plugged 0.088
And Tor is ready 50.117
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.670
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.165
Given I shutdown Tails and wait for the computer to power off 11.626
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:31.577
Then Tails is running version 6.2~testoverlayfs 0.040
And all tps features are active 2.857
And the file system changes introduced in version 6.2~testoverlayfs are present 0.370
And only the 6.2~testoverlayfs SquashFS delta is installed 0.102
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.381
# 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.372
When the network is plugged 0.113
And Tor is ready 19.412
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.088
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.043
Given I shutdown Tails and wait for the computer to power off 6.664
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.485
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.617
And the file system changes introduced in version 6.3~testoverlayfs are present 0.565
And only the 6.3~testoverlayfs SquashFS delta is installed 0.107
# 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.391
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.316
When the network is plugged 0.091
And Tor is ready 16.908
Then the Upgrader considers the system as up-to-date 10.804
# 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.467
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.048
After features/support/hooks.rb:326 0.826
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
40.386
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.222
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.561
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.084
And the signing key used by the Upgrader is outdated 0.891
But a current signing key is available on our website 0.000
When the network is plugged 0.189
And Tor is ready 18.409
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.028
After features/support/hooks.rb:326 1.387
After features/support/hooks.rb:100 0.000