Project Number Date
test_Tails_ISO_devel 3627 30 Dec 2024, 12: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 19:6.419 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:11.089
Before features/support/hooks.rb:269 0.006
Given a computer 0.245
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 28.871
When I start Tails from USB drive "old" with network unplugged 1:36.779
Then the boot device has safe access rights 3.016
And Tails is running from USB drive "old" 0.316
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.089
And udev-watchdog is monitoring the correct device 0.300
And I unplug USB drive "old" 0.293
After features/support/hooks.rb:326 7.820
After features/support/hooks.rb:100 0.008
Tags: @product
2:4.209
Before features/support/hooks.rb:269 0.006
Given a computer 0.218
And I start Tails from USB drive "old" with network unplugged and I login 1:21.046
Then Tails is running from USB drive "old" 0.357
And I create a persistent partition 31.577
And I take note of which tps features are available 2.029
Then a Tails persistence partition exists on USB drive "old" 0.748
And I shutdown Tails and wait for the computer to power off 8.231
After features/support/hooks.rb:326 0.185
After features/support/hooks.rb:100 0.010
Tags: @product
2:44.277
Before features/support/hooks.rb:269 0.005
Given a computer 0.205
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:7.631
Then Tails is running from USB drive "old" 0.583
And all tps features are active 2.010
When I write some files expected to persist 1.740
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.206
And all persistence configuration files have safe access rights 0.376
And all persistent directories from the old Tails version have safe access rights 2.690
And I take note of which tps features are available 0.436
And I shutdown Tails and wait for the computer to power off 4.281
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.114
After features/support/hooks.rb:326 0.168
After features/support/hooks.rb:100 0.008
Tags: @product
2:34.097
Before features/support/hooks.rb:269 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 11.439
And I log in to a new session 19.253
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.769
And I plug USB drive "to_upgrade" 2.380
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.012
Then the running Tails is installed on USB drive "to_upgrade" 24.789
And I unplug USB drive "to_upgrade" 0.223
And I unplug USB drive "__internal" 0.228
After features/support/hooks.rb:326 2.034
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.070
Before features/support/hooks.rb:269 0.007
Given a computer 0.225
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.596
Then all tps features from the old Tails version are active 1.969
And Tails is running from USB drive "to_upgrade" 0.343
And the boot device has safe access rights 3.060
And the expected persistent files created with the old Tails version are present in the filesystem 1.502
And all persistent directories from the old Tails version have safe access rights 2.371
After features/support/hooks.rb:326 1.475
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:39.189
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.776
And no SquashFS delta is installed 0.240
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.816
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.085
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.283
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.479
When the network is plugged 0.089
And Tor is ready 21.492
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.279
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.766
Given I shutdown Tails and wait for the computer to power off 8.523
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.090
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.177
And the file system changes introduced in version 6.2~testoverlayfs are present 0.308
And only the 6.2~testoverlayfs SquashFS delta is installed 0.081
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.317
# 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.382
When the network is plugged 0.103
And Tor is ready 20.731
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.283
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.622
Given I shutdown Tails and wait for the computer to power off 4.270
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.122
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.280
And the file system changes introduced in version 6.3~testoverlayfs are present 0.510
And only the 6.3~testoverlayfs SquashFS delta is installed 0.077
# 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.311
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.278
When the network is plugged 0.066
And Tor is ready 17.346
Then the Upgrader considers the system as up-to-date 10.856
# 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.030
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.079
After features/support/hooks.rb:326 0.681
After features/support/hooks.rb:100 0.031
Tags: @product @automatic_upgrade
36.485
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 10.882
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.374
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the signing key used by the Upgrader is outdated 0.849
But a current signing key is available on our website 0.000
When the network is plugged 0.095
And Tor is ready 17.852
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.358
After features/support/hooks.rb:326 1.062
After features/support/hooks.rb:100 0.000