Project Number Date
test_Tails_ISO_stable 5311 04 Dec 2024, 08:39

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:11.463 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:21.729
Before features/support/hooks.rb:269 0.005
Given a computer 0.186
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 29.849
When I start Tails from USB drive "old" with network unplugged 1:46.309
Then the boot device has safe access rights 3.187
And Tails is running from USB drive "old" 0.366
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.109
And udev-watchdog is monitoring the correct device 0.352
And I unplug USB drive "old" 0.208
After features/support/hooks.rb:326 3.609
After features/support/hooks.rb:100 0.008
Tags: @product
2:8.127
Before features/support/hooks.rb:269 0.004
Given a computer 0.212
And I start Tails from USB drive "old" with network unplugged and I login 1:23.361
Then Tails is running from USB drive "old" 0.374
And I create a persistent partition 32.778
And I take note of which tps features are available 1.804
Then a Tails persistence partition exists on USB drive "old" 0.924
And I shutdown Tails and wait for the computer to power off 8.672
After features/support/hooks.rb:326 0.196
After features/support/hooks.rb:100 0.010
Tags: @product
2:55.069
Before features/support/hooks.rb:269 0.008
Given a computer 0.223
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.823
Then Tails is running from USB drive "old" 0.389
And all tps features are active 2.376
When I write some files expected to persist 1.670
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.239
And all persistence configuration files have safe access rights 0.410
And all persistent directories from the old Tails version have safe access rights 2.471
And I take note of which tps features are available 0.499
And I shutdown Tails and wait for the computer to power off 4.469
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.492
After features/support/hooks.rb:326 0.132
After features/support/hooks.rb:100 0.009
Tags: @product
2:30.698
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.050
And I log in to a new session 19.702
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.859
And I plug USB drive "to_upgrade" 2.494
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.895
Then the running Tails is installed on USB drive "to_upgrade" 21.282
And I unplug USB drive "to_upgrade" 0.200
And I unplug USB drive "__internal" 0.213
After features/support/hooks.rb:326 1.942
After features/support/hooks.rb:100 0.000
Tags: @product
2:10.306
Before features/support/hooks.rb:269 0.006
Given a computer 0.314
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:0.806
Then all tps features from the old Tails version are active 1.480
And Tails is running from USB drive "to_upgrade" 0.377
And the boot device has safe access rights 3.459
And the expected persistent files created with the old Tails version are present in the filesystem 1.396
And all persistent directories from the old Tails version have safe access rights 2.472
After features/support/hooks.rb:326 0.705
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:21.880
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 12.273
And no SquashFS delta is installed 0.091
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.364
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.302
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.503
When the network is plugged 0.092
And Tor is ready 23.289
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.667
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.176
Given I shutdown Tails and wait for the computer to power off 8.605
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.456
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.625
And the file system changes introduced in version 6.2~testoverlayfs are present 0.325
And only the 6.2~testoverlayfs SquashFS delta is installed 0.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.320
# 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.264
When the network is plugged 0.059
And Tor is ready 19.420
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.099
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.832
Given I shutdown Tails and wait for the computer to power off 4.334
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.754
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.876
And the file system changes introduced in version 6.3~testoverlayfs are present 0.444
And only the 6.3~testoverlayfs SquashFS delta is installed 0.084
# 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.361
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.436
When the network is plugged 0.085
And Tor is ready 18.172
Then the Upgrader considers the system as up-to-date 0.304
# 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 15.571
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.526
After features/support/hooks.rb:326 0.798
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
43.651
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 14.686
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.287
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.908
But a current signing key is available on our website 0.000
When the network is plugged 0.079
And Tor is ready 21.106
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.521
After features/support/hooks.rb:326 0.662
After features/support/hooks.rb:100 0.000