Project Number Date
test_Tails_ISO_devel 3559 23 Oct 2024, 13:01

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:19.935 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:6.402
Before features/support/hooks.rb:269 0.004
Given a computer 0.195
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 31.806
When I start Tails from USB drive "old" with network unplugged 1:29.064
Then the boot device has safe access rights 3.205
And Tails is running from USB drive "old" 0.365
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.309
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:326 3.782
After features/support/hooks.rb:100 0.012
Tags: @product
2:5.307
Before features/support/hooks.rb:269 0.005
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login 1:21.707
Then Tails is running from USB drive "old" 0.318
And I create a persistent partition 32.617
And I take note of which tps features are available 1.445
Then a Tails persistence partition exists on USB drive "old" 0.851
And I shutdown Tails and wait for the computer to power off 8.171
After features/support/hooks.rb:326 0.161
After features/support/hooks.rb:100 0.010
Tags: @product
2:58.352
Before features/support/hooks.rb:269 0.006
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.936
Then Tails is running from USB drive "old" 0.321
And all tps features are active 2.330
When I write some files expected to persist 1.602
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.216
And all persistence configuration files have safe access rights 0.374
And all persistent directories from the old Tails version have safe access rights 2.346
And I take note of which tps features are available 0.445
And I shutdown Tails and wait for the computer to power off 4.297
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.291
After features/support/hooks.rb:326 0.123
After features/support/hooks.rb:100 0.011
Tags: @product
2:29.575
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.693
And I log in to a new session 19.997
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.691
And I plug USB drive "to_upgrade" 2.387
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.241
Then the running Tails is installed on USB drive "to_upgrade" 21.173
And I unplug USB drive "to_upgrade" 0.196
And I unplug USB drive "__internal" 0.194
After features/support/hooks.rb:326 2.250
After features/support/hooks.rb:100 0.000
Tags: @product
2:23.498
Before features/support/hooks.rb:269 0.004
Given a computer 0.182
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.011
Then all tps features from the old Tails version are active 1.763
And Tails is running from USB drive "to_upgrade" 0.351
And the boot device has safe access rights 3.387
And the expected persistent files created with the old Tails version are present in the filesystem 1.414
And all persistent directories from the old Tails version have safe access rights 2.387
After features/support/hooks.rb:326 0.800
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:41.048
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 11.990
And no SquashFS delta is installed 0.081
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.313
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.553
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.451
When the network is plugged 0.065
And Tor is ready 18.592
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.523
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.204
Given I shutdown Tails and wait for the computer to power off 1:17.778
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.634
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.182
And the file system changes introduced in version 6.2~testoverlayfs are present 0.317
And only the 6.2~testoverlayfs SquashFS delta is installed 0.097
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.400
# 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.314
When the network is plugged 0.080
And Tor is ready 47.050
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.588
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.387
Given I shutdown Tails and wait for the computer to power off 4.408
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.923
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.218
And the file system changes introduced in version 6.3~testoverlayfs are present 0.596
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.325
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.366
When the network is plugged 0.096
And Tor is ready 17.722
Then the Upgrader considers the system as up-to-date 0.329
# 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.358
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.933
After features/support/hooks.rb:326 0.677
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
35.751
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.881
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.310
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the signing key used by the Upgrader is outdated 0.820
But a current signing key is available on our website 0.000
When the network is plugged 0.072
And Tor is ready 18.220
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.370
After features/support/hooks.rb:326 1.230
After features/support/hooks.rb:100 0.000