Project Number Date
test_Tails_ISO_stable 5313 04 Dec 2024, 23:21

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:5.589 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:17.455
Before features/support/hooks.rb:269 0.004
Given a computer 0.209
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 28.242
When I start Tails from USB drive "old" with network unplugged 1:43.837
Then the boot device has safe access rights 3.077
And Tails is running from USB drive "old" 0.343
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.116
And udev-watchdog is monitoring the correct device 0.289
And I unplug USB drive "old" 0.181
After features/support/hooks.rb:326 7.262
After features/support/hooks.rb:100 0.009
Tags: @product
2:8.395
Before features/support/hooks.rb:269 0.006
Given a computer 0.234
And I start Tails from USB drive "old" with network unplugged and I login 1:24.366
Then Tails is running from USB drive "old" 0.354
And I create a persistent partition 34.512
And I take note of which tps features are available 1.494
Then a Tails persistence partition exists on USB drive "old" 0.845
And I shutdown Tails and wait for the computer to power off 6.588
After features/support/hooks.rb:326 0.173
After features/support/hooks.rb:100 0.009
Tags: @product
2:52.674
Before features/support/hooks.rb:269 0.006
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.214
Then Tails is running from USB drive "old" 0.428
And all tps features are active 1.814
When I write some files expected to persist 3.105
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.214
And all persistence configuration files have safe access rights 0.355
And all persistent directories from the old Tails version have safe access rights 2.348
And I take note of which tps features are available 0.428
And I shutdown Tails and wait for the computer to power off 4.489
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.086
After features/support/hooks.rb:326 0.135
After features/support/hooks.rb:100 0.012
Tags: @product
2:27.076
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.529
And I log in to a new session 18.625
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.521
And I plug USB drive "to_upgrade" 2.474
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.473
Then the running Tails is installed on USB drive "to_upgrade" 20.028
And I unplug USB drive "to_upgrade" 0.195
And I unplug USB drive "__internal" 0.229
After features/support/hooks.rb:326 7.065
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.087
Before features/support/hooks.rb:269 0.006
Given a computer 0.189
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.945
Then all tps features from the old Tails version are active 1.572
And Tails is running from USB drive "to_upgrade" 0.357
And the boot device has safe access rights 3.329
And the expected persistent files created with the old Tails version are present in the filesystem 1.344
And all persistent directories from the old Tails version have safe access rights 2.348
After features/support/hooks.rb:326 0.833
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
6:18.852
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 11.542
And no SquashFS delta is installed 0.127
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.559
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.328
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.469
When the network is plugged 0.080
And Tor is ready 22.213
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.342
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.726
Given I shutdown Tails and wait for the computer to power off 10.660
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.270
Then Tails is running version 6.2~testoverlayfs 0.021
And all tps features are active 2.511
And the file system changes introduced in version 6.2~testoverlayfs are present 0.299
And only the 6.2~testoverlayfs SquashFS delta is installed 0.098
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.303
# 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.262
When the network is plugged 0.068
And Tor is ready 17.613
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.570
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.592
Given I shutdown Tails and wait for the computer to power off 4.265
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.672
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.065
And the file system changes introduced in version 6.3~testoverlayfs are present 0.428
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.322
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.323
When the network is plugged 0.098
And Tor is ready 19.429
Then the Upgrader considers the system as up-to-date 0.299
# 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.764
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.372
After features/support/hooks.rb:326 0.754
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
37.049
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.286
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.382
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the signing key used by the Upgrader is outdated 0.818
But a current signing key is available on our website 0.000
When the network is plugged 0.083
And Tor is ready 20.496
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.909
After features/support/hooks.rb:326 1.426
After features/support/hooks.rb:100 0.000