Project Number Date
test_Tails_ISO_stable 4787 14 Apr 2024, 11:54

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 16:56.368 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
1:35.601
Before features/support/hooks.rb:259 0.004
Given a computer 0.169
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.044
And I write an old version of the Tails USB image to disk "old" 20.011
When I start Tails from USB drive "old" with network unplugged 1:10.376
Then the boot device has safe access rights 2.989
And Tails is running from USB drive "old" 0.315
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.278
And I unplug USB drive "old" 0.208
After features/support/hooks.rb:305 6.634
After features/support/hooks.rb:89 0.009
Tags: @product
1:55.260
Before features/support/hooks.rb:259 0.006
Given a computer 0.284
And I start Tails from USB drive "old" with network unplugged and I login 1:13.055
Then Tails is running from USB drive "old" 0.331
And I create a persistent partition 33.178
And I take note of which tps features are available 1.245
Then a Tails persistence partition exists on USB drive "old" 0.933
And I shutdown Tails and wait for the computer to power off 6.231
After features/support/hooks.rb:305 0.167
After features/support/hooks.rb:89 0.009
Tags: @product
2:21.996
Before features/support/hooks.rb:259 0.006
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:55.260
Then Tails is running from USB drive "old" 0.393
And all tps features are active 1.826
When I write some files expected to persist 1.732
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.350
And all persistence configuration files have safe access rights 0.359
And all persistent directories from the old Tails version have safe access rights 2.473
And I take note of which tps features are available 0.462
And I shutdown Tails and wait for the computer to power off 4.122
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.825
After features/support/hooks.rb:305 0.120
After features/support/hooks.rb:89 0.009
Tags: @product
2:22.441
Before features/support/hooks.rb:259 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 10.098
And I log in to a new session 17.052
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.220
And I plug USB drive "to_upgrade" 2.488
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.172
Then the running Tails is installed on USB drive "to_upgrade" 17.045
And I unplug USB drive "to_upgrade" 0.187
And I unplug USB drive "__internal" 0.176
After features/support/hooks.rb:305 2.066
After features/support/hooks.rb:89 0.000
Tags: @product
1:59.249
Before features/support/hooks.rb:259 0.006
Given a computer 0.170
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:50.331
Then all tps features from the old Tails version are active 1.545
And Tails is running from USB drive "to_upgrade" 0.330
And the boot device has safe access rights 2.913
And the expected persistent files created with the old Tails version are present in the filesystem 1.532
And all persistent directories from the old Tails version have safe access rights 2.425
After features/support/hooks.rb:305 0.803
After features/support/hooks.rb:89 0.018
Tags: @product @automatic_upgrade
6:9.369
Before features/support/hooks.rb:259 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.499
And no SquashFS delta is installed 0.091
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.278
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.366
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.454
When the network is plugged 0.037
And Tor is ready 45.649
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.587
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.278
Given I shutdown Tails and wait for the computer to power off 6.700
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.577
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.205
And the file system changes introduced in version 6.2~testoverlayfs are present 0.274
And only the 6.2~testoverlayfs SquashFS delta is installed 0.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.287
# 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.255
When the network is plugged 0.049
And Tor is ready 18.712
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.086
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.535
Given I shutdown Tails and wait for the computer to power off 4.378
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:48.225
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.797
And the file system changes introduced in version 6.3~testoverlayfs are present 0.433
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.285
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.230
When the network is plugged 0.043
And Tor is ready 17.602
Then the Upgrader considers the system as up-to-date 0.226
# 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 13.128
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.881
After features/support/hooks.rb:305 0.956
After features/support/hooks.rb:89 0.014
Tags: @product @automatic_upgrade
32.450
Before features/support/hooks.rb:259 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.321
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.291
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the signing key used by the Upgrader is outdated 0.433
But a current signing key is available on our website 0.000
When the network is plugged 0.047
And Tor is ready 17.332
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.967
After features/support/hooks.rb:305 0.735
After features/support/hooks.rb:89 0.000