Project Number Date
test_Tails_ISO_stable 5210 22 Oct 2024, 08:23

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 18:18.018 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
1:58.083
Before features/support/hooks.rb:269 0.005
Given a computer 0.180
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 29.554
When I start Tails from USB drive "old" with network unplugged 1:23.245
Then the boot device has safe access rights 3.039
And Tails is running from USB drive "old" 0.305
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.313
And I unplug USB drive "old" 0.176
After features/support/hooks.rb:326 3.499
After features/support/hooks.rb:100 0.009
Tags: @product
2:14.301
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 1:33.698
Then Tails is running from USB drive "old" 0.319
And I create a persistent partition 31.482
And I take note of which tps features are available 1.507
Then a Tails persistence partition exists on USB drive "old" 0.792
And I shutdown Tails and wait for the computer to power off 6.312
After features/support/hooks.rb:326 0.174
After features/support/hooks.rb:100 0.024
Tags: @product
2:52.394
Before features/support/hooks.rb:269 0.006
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.931
Then Tails is running from USB drive "old" 0.489
And all tps features are active 1.907
When I write some files expected to persist 1.707
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.200
And all persistence configuration files have safe access rights 0.408
And all persistent directories from the old Tails version have safe access rights 2.634
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.284
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.209
After features/support/hooks.rb:326 0.126
After features/support/hooks.rb:100 0.009
Tags: @product
2:27.047
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 10.950
And I log in to a new session 18.412
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.661
And I plug USB drive "to_upgrade" 2.445
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.233
Then the running Tails is installed on USB drive "to_upgrade" 19.945
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.195
After features/support/hooks.rb:326 2.075
After features/support/hooks.rb:100 0.000
Tags: @product
2:8.827
Before features/support/hooks.rb:269 0.005
Given a computer 0.195
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:59.551
Then all tps features from the old Tails version are active 1.714
And Tails is running from USB drive "to_upgrade" 0.298
And the boot device has safe access rights 3.128
And the expected persistent files created with the old Tails version are present in the filesystem 1.482
And all persistent directories from the old Tails version have safe access rights 2.457
After features/support/hooks.rb:326 0.935
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:1.950
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.806
And no SquashFS delta is installed 0.092
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.275
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.086
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.333
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.464
When the network is plugged 0.084
And Tor is ready 21.419
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.525
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.635
Given I shutdown Tails and wait for the computer to power off 8.755
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.035
Then Tails is running version 6.2~testoverlayfs 0.025
And all tps features are active 2.344
And the file system changes introduced in version 6.2~testoverlayfs are present 0.329
And only the 6.2~testoverlayfs SquashFS delta is installed 0.089
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.315
# 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.296
When the network is plugged 0.092
And Tor is ready 18.657
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.003
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.396
Given I shutdown Tails and wait for the computer to power off 4.276
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.243
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.147
And the file system changes introduced in version 6.3~testoverlayfs are present 0.484
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.306
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.236
When the network is plugged 0.065
And Tor is ready 18.447
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 13.360
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.928
After features/support/hooks.rb:326 0.790
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
35.413
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 9.755
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.509
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.725
But a current signing key is available on our website 0.000
When the network is plugged 0.075
And Tor is ready 19.082
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.208
After features/support/hooks.rb:326 0.902
After features/support/hooks.rb:100 0.000