Project Number Date
test_Tails_ISO_devel 3378 07 May 2024, 12:36

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:15.624 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:5.441
Before features/support/hooks.rb:259 0.008
Given a computer 0.206
And I create a 7200 MiB disk named "old" 0.084
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 31.325
When I start Tails from USB drive "old" with network unplugged 1:28.618
Then the boot device has safe access rights 3.080
And Tails is running from USB drive "old" 0.355
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.101
And udev-watchdog is monitoring the correct device 0.331
And I unplug USB drive "old" 0.204
After features/support/hooks.rb:305 3.542
After features/support/hooks.rb:89 0.009
Tags: @product
2:11.555
Before features/support/hooks.rb:259 0.007
Given a computer 0.219
And I start Tails from USB drive "old" with network unplugged and I login 1:25.621
Then Tails is running from USB drive "old" 0.374
And I create a persistent partition 34.501
And I take note of which tps features are available 1.540
Then a Tails persistence partition exists on USB drive "old" 0.855
And I shutdown Tails and wait for the computer to power off 8.442
After features/support/hooks.rb:305 0.177
After features/support/hooks.rb:89 0.010
Tags: @product
2:55.781
Before features/support/hooks.rb:259 0.005
Given a computer 0.211
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.398
Then Tails is running from USB drive "old" 0.360
And all tps features are active 2.341
When I write some files expected to persist 1.844
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.251
And all persistence configuration files have safe access rights 0.467
And all persistent directories from the old Tails version have safe access rights 3.100
And I take note of which tps features are available 0.480
And I shutdown Tails and wait for the computer to power off 4.418
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.907
After features/support/hooks.rb:305 0.149
After features/support/hooks.rb:89 0.011
Tags: @product
2:28.123
Before features/support/hooks.rb:259 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 12.759
And I log in to a new session 19.171
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.511
And I plug USB drive "to_upgrade" 2.442
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.389
Then the running Tails is installed on USB drive "to_upgrade" 15.393
And I unplug USB drive "to_upgrade" 0.281
And I unplug USB drive "__internal" 0.174
After features/support/hooks.rb:305 2.501
After features/support/hooks.rb:89 0.000
Tags: @product
2:18.669
Before features/support/hooks.rb:259 0.008
Given a computer 0.257
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.683
Then all tps features from the old Tails version are active 1.613
And Tails is running from USB drive "to_upgrade" 0.344
And the boot device has safe access rights 3.114
And the expected persistent files created with the old Tails version are present in the filesystem 1.486
And all persistent directories from the old Tails version have safe access rights 2.169
After features/support/hooks.rb:305 0.672
After features/support/hooks.rb:89 0.009
Tags: @product @automatic_upgrade
6:27.801
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.632
And no SquashFS delta is installed 0.100
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.401
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.263
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.479
When the network is plugged 0.033
And Tor is ready 19.554
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.427
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.133
Given I shutdown Tails and wait for the computer to power off 8.922
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.591
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.316
And the file system changes introduced in version 6.2~testoverlayfs are present 0.314
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.324
# 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.296
When the network is plugged 0.047
And Tor is ready 18.006
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.463
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.094
Given I shutdown Tails and wait for the computer to power off 4.290
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.482
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.326
And the file system changes introduced in version 6.3~testoverlayfs are present 0.490
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.452
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.291
When the network is plugged 0.050
And Tor is ready 18.774
Then the Upgrader considers the system as up-to-date 0.321
# 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.875
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.817
After features/support/hooks.rb:305 0.831
After features/support/hooks.rb:89 0.017
Tags: @product @automatic_upgrade
48.250
Before features/support/hooks.rb:259 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 24.097
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.421
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.580
But a current signing key is available on our website 0.000
When the network is plugged 0.049
And Tor is ready 18.045
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.006
After features/support/hooks.rb:305 0.746
After features/support/hooks.rb:89 0.000