Project Number Date
test_Tails_ISO_devel 3404 29 May 2024, 13:26

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 22:0.552 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:42.383
Before features/support/hooks.rb:259 0.008
Given a computer 0.268
And I create a 7200 MiB disk named "old" 0.073
And I plug USB drive "old" 1.067
And I write an old version of the Tails USB image to disk "old" 1:4.624
When I start Tails from USB drive "old" with network unplugged 1:32.009
Then the boot device has safe access rights 3.278
And Tails is running from USB drive "old" 0.341
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.365
And I unplug USB drive "old" 0.184
After features/support/hooks.rb:305 3.615
After features/support/hooks.rb:89 0.074
Tags: @product
2:22.387
Before features/support/hooks.rb:259 0.019
Given a computer 0.249
And I start Tails from USB drive "old" with network unplugged and I login 1:29.420
Then Tails is running from USB drive "old" 0.457
And I create a persistent partition 39.807
And I take note of which tps features are available 2.600
Then a Tails persistence partition exists on USB drive "old" 0.917
And I shutdown Tails and wait for the computer to power off 8.935
After features/support/hooks.rb:305 0.303
After features/support/hooks.rb:89 0.010
Tags: @product
3:1.274
Before features/support/hooks.rb:259 0.006
Given a computer 0.308
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.343
Then Tails is running from USB drive "old" 0.355
And all tps features are active 3.314
When I write some files expected to persist 1.704
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.238
And all persistence configuration files have safe access rights 0.470
And all persistent directories from the old Tails version have safe access rights 2.670
And I take note of which tps features are available 0.657
And I shutdown Tails and wait for the computer to power off 4.290
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.919
After features/support/hooks.rb:305 0.155
After features/support/hooks.rb:89 0.013
Tags: @product
2:48.339
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 13.348
And I log in to a new session 20.236
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.631
And I plug USB drive "to_upgrade" 2.415
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.000
Then the running Tails is installed on USB drive "to_upgrade" 29.221
And I unplug USB drive "to_upgrade" 0.268
And I unplug USB drive "__internal" 0.217
After features/support/hooks.rb:305 3.597
After features/support/hooks.rb:89 0.000
Tags: @product
2:48.483
Before features/support/hooks.rb:259 0.007
Given a computer 0.249
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:35.169
Then all tps features from the old Tails version are active 2.889
And Tails is running from USB drive "to_upgrade" 0.515
And the boot device has safe access rights 4.696
And the expected persistent files created with the old Tails version are present in the filesystem 1.804
And all persistent directories from the old Tails version have safe access rights 3.159
After features/support/hooks.rb:305 1.073
After features/support/hooks.rb:89 0.262
Tags: @product @automatic_upgrade
7:15.250
Before features/support/hooks.rb:259 0.149
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 23.620
And no SquashFS delta is installed 0.091
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.467
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.332
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.593
When the network is plugged 0.051
And Tor is ready 22.398
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.755
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.593
Given I shutdown Tails and wait for the computer to power off 10.885
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:21.246
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.806
And the file system changes introduced in version 6.2~testoverlayfs are present 0.384
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.350
# 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.298
When the network is plugged 0.051
And Tor is ready 18.390
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.458
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.378
Given I shutdown Tails and wait for the computer to power off 4.486
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.443
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.732
And the file system changes introduced in version 6.3~testoverlayfs are present 0.583
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.371
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.325
When the network is plugged 0.053
And Tor is ready 19.140
Then the Upgrader considers the system as up-to-date 0.372
# 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 16.254
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.073
After features/support/hooks.rb:305 0.807
After features/support/hooks.rb:89 0.028
Tags: @product @automatic_upgrade
1:2.433
Before features/support/hooks.rb:259 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.219
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.366
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.088
And the signing key used by the Upgrader is outdated 0.543
But a current signing key is available on our website 0.000
When the network is plugged 0.056
And Tor is ready 47.386
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.771
After features/support/hooks.rb:305 1.311
After features/support/hooks.rb:89 0.000