Project Number Date
test_Tails_ISO_stable 5352 23 Dec 2024, 12:24

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 20:23.426 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:1.336
Before features/support/hooks.rb:269 0.004
Given a computer 0.196
And I create a 7200 MiB disk named "old" 0.040
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 30.508
When I start Tails from USB drive "old" with network unplugged 1:25.600
Then the boot device has safe access rights 2.954
And Tails is running from USB drive "old" 0.321
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.300
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:326 6.953
After features/support/hooks.rb:100 0.011
Tags: @product
2:5.607
Before features/support/hooks.rb:269 0.006
Given a computer 0.201
And I start Tails from USB drive "old" with network unplugged and I login 1:23.282
Then Tails is running from USB drive "old" 0.365
And I create a persistent partition 31.051
And I take note of which tps features are available 1.530
Then a Tails persistence partition exists on USB drive "old" 0.886
And I shutdown Tails and wait for the computer to power off 8.288
After features/support/hooks.rb:326 0.138
After features/support/hooks.rb:100 0.008
Tags: @product
2:58.694
Before features/support/hooks.rb:269 0.005
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.398
Then Tails is running from USB drive "old" 0.329
And all tps features are active 1.896
When I write some files expected to persist 2.175
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.218
And all persistence configuration files have safe access rights 0.378
And all persistent directories from the old Tails version have safe access rights 2.437
And I take note of which tps features are available 0.458
And I shutdown Tails and wait for the computer to power off 4.301
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.917
After features/support/hooks.rb:326 0.105
After features/support/hooks.rb:100 0.007
Tags: @product
2:28.309
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 10.858
And I log in to a new session 18.374
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.606
And I plug USB drive "to_upgrade" 2.474
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.566
Then the running Tails is installed on USB drive "to_upgrade" 21.012
And I unplug USB drive "to_upgrade" 0.197
And I unplug USB drive "__internal" 0.217
After features/support/hooks.rb:326 2.534
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.952
Before features/support/hooks.rb:269 0.006
Given a computer 0.188
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.146
Then all tps features from the old Tails version are active 1.557
And Tails is running from USB drive "to_upgrade" 0.297
And the boot device has safe access rights 2.966
And the expected persistent files created with the old Tails version are present in the filesystem 1.380
And all persistent directories from the old Tails version have safe access rights 2.416
After features/support/hooks.rb:326 0.783
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:35.763
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.535
And no SquashFS delta is installed 0.090
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.571
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.278
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.458
When the network is plugged 0.155
And Tor is ready 22.440
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.546
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.006
Given I shutdown Tails and wait for the computer to power off 1:12.067
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.291
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.347
And the file system changes introduced in version 6.2~testoverlayfs are present 0.356
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.299
# 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.323
When the network is plugged 0.103
And Tor is ready 21.492
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.091
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.464
Given I shutdown Tails and wait for the computer to power off 4.273
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.763
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.045
And the file system changes introduced in version 6.3~testoverlayfs are present 0.521
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.298
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.235
When the network is plugged 0.078
And Tor is ready 20.008
Then the Upgrader considers the system as up-to-date 0.293
# 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.190
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.912
After features/support/hooks.rb:326 0.766
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
57.763
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.452
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.313
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.241
And the signing key used by the Upgrader is outdated 0.061
But a current signing key is available on our website 0.000
When the network is plugged 0.076
And Tor is ready 46.036
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.581
After features/support/hooks.rb:326 0.628
After features/support/hooks.rb:100 0.000