Project Number Date
test_Tails_ISO_stable 5314 05 Dec 2024, 08: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:17.313 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:20.883
Before features/support/hooks.rb:269 0.006
Given a computer 0.181
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 32.020
When I start Tails from USB drive "old" with network unplugged 1:43.071
Then the boot device has safe access rights 3.297
And Tails is running from USB drive "old" 0.342
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.121
And udev-watchdog is monitoring the correct device 0.325
And I unplug USB drive "old" 0.363
After features/support/hooks.rb:326 3.603
After features/support/hooks.rb:100 0.010
Tags: @product
2:12.193
Before features/support/hooks.rb:269 0.006
Given a computer 0.215
And I start Tails from USB drive "old" with network unplugged and I login 1:26.731
Then Tails is running from USB drive "old" 0.353
And I create a persistent partition 34.005
And I take note of which tps features are available 1.545
Then a Tails persistence partition exists on USB drive "old" 0.973
And I shutdown Tails and wait for the computer to power off 8.368
After features/support/hooks.rb:326 0.147
After features/support/hooks.rb:100 0.008
Tags: @product
3:1.550
Before features/support/hooks.rb:269 0.005
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.935
Then Tails is running from USB drive "old" 0.338
And all tps features are active 2.258
When I write some files expected to persist 1.658
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.233
And all persistence configuration files have safe access rights 0.375
And all persistent directories from the old Tails version have safe access rights 2.389
And I take note of which tps features are available 0.408
And I shutdown Tails and wait for the computer to power off 4.496
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.274
After features/support/hooks.rb:326 0.120
After features/support/hooks.rb:100 0.008
Tags: @product
2:31.067
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.702
And I log in to a new session 19.558
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.625
And I plug USB drive "to_upgrade" 2.402
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.264
Then the running Tails is installed on USB drive "to_upgrade" 21.089
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.222
After features/support/hooks.rb:326 2.185
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.750
Before features/support/hooks.rb:269 0.005
Given a computer 0.205
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.178
Then all tps features from the old Tails version are active 1.667
And Tails is running from USB drive "to_upgrade" 0.327
And the boot device has safe access rights 3.473
And the expected persistent files created with the old Tails version are present in the filesystem 1.490
And all persistent directories from the old Tails version have safe access rights 2.406
After features/support/hooks.rb:326 1.393
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:13.655
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.704
And no SquashFS delta is installed 0.480
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.454
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.288
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.443
When the network is plugged 0.084
And Tor is ready 21.574
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.732
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.597
Given I shutdown Tails and wait for the computer to power off 8.665
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.027
Then Tails is running version 6.2~testoverlayfs 0.032
And all tps features are active 2.156
And the file system changes introduced in version 6.2~testoverlayfs are present 0.330
And only the 6.2~testoverlayfs SquashFS delta is installed 0.083
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.297
# 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.280
When the network is plugged 0.079
And Tor is ready 21.364
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.023
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.706
Given I shutdown Tails and wait for the computer to power off 4.357
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.051
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.955
And the file system changes introduced in version 6.3~testoverlayfs are present 0.505
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.320
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.291
When the network is plugged 0.072
And Tor is ready 17.639
Then the Upgrader considers the system as up-to-date 0.342
# 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.513
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.039
After features/support/hooks.rb:326 0.754
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
38.212
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.558
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.307
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.079
And the signing key used by the Upgrader is outdated 0.899
But a current signing key is available on our website 0.000
When the network is plugged 0.064
And Tor is ready 20.353
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.948
After features/support/hooks.rb:326 0.901
After features/support/hooks.rb:100 0.000