Project Number Date
test_Tails_ISO_stable 5144 05 Oct 2024, 08:43

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:1.390 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:3.342
Before features/support/hooks.rb:269 0.004
Given a computer 0.178
And I create a 7200 MiB disk named "old" 0.055
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 30.975
When I start Tails from USB drive "old" with network unplugged 1:27.021
Then the boot device has safe access rights 3.065
And Tails is running from USB drive "old" 0.326
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.308
And I unplug USB drive "old" 0.202
After features/support/hooks.rb:326 8.031
After features/support/hooks.rb:100 0.007
Tags: @product
2:7.999
Before features/support/hooks.rb:269 0.005
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login 1:22.308
Then Tails is running from USB drive "old" 0.386
And I create a persistent partition 34.357
And I take note of which tps features are available 1.588
Then a Tails persistence partition exists on USB drive "old" 0.842
And I shutdown Tails and wait for the computer to power off 8.321
After features/support/hooks.rb:326 0.140
After features/support/hooks.rb:100 0.007
Tags: @product
3:4.448
Before features/support/hooks.rb:269 0.004
Given a computer 0.217
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.590
Then Tails is running from USB drive "old" 1.515
And all tps features are active 2.110
When I write some files expected to persist 3.624
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.217
And all persistence configuration files have safe access rights 0.367
And all persistent directories from the old Tails version have safe access rights 2.545
And I take note of which tps features are available 0.683
And I shutdown Tails and wait for the computer to power off 6.298
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.279
After features/support/hooks.rb:326 0.172
After features/support/hooks.rb:100 0.011
Tags: @product
2:36.306
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 12.517
And I log in to a new session 20.743
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.966
And I plug USB drive "to_upgrade" 2.529
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.021
Then the running Tails is installed on USB drive "to_upgrade" 24.039
And I unplug USB drive "to_upgrade" 0.265
And I unplug USB drive "__internal" 0.223
After features/support/hooks.rb:326 3.539
After features/support/hooks.rb:100 0.000
Tags: @product
2:29.205
Before features/support/hooks.rb:269 0.009
Given a computer 0.238
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:19.212
Then all tps features from the old Tails version are active 1.945
And Tails is running from USB drive "to_upgrade" 0.327
And the boot device has safe access rights 3.552
And the expected persistent files created with the old Tails version are present in the filesystem 1.512
And all persistent directories from the old Tails version have safe access rights 2.417
After features/support/hooks.rb:326 0.690
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
7:2.510
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 45.140
And no SquashFS delta is installed 0.341
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.516
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.132
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.311
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.458
When the network is plugged 0.077
And Tor is ready 24.850
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.704
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.877
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 1:59.823
Then Tails is running version 6.2~testoverlayfs 0.022
And all tps features are active 2.256
And the file system changes introduced in version 6.2~testoverlayfs are present 0.345
And only the 6.2~testoverlayfs SquashFS delta is installed 0.091
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.325
# 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.083
And Tor is ready 20.902
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.127
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.133
Given I shutdown Tails and wait for the computer to power off 6.164
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.027
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.121
And the file system changes introduced in version 6.3~testoverlayfs are present 0.522
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.398
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.323
When the network is plugged 0.101
And Tor is ready 21.510
Then the Upgrader considers the system as up-to-date 0.307
# 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.296
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.145
After features/support/hooks.rb:326 0.839
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
37.577
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.807
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.336
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 0.941
But a current signing key is available on our website 0.000
When the network is plugged 0.082
And Tor is ready 17.032
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.311
After features/support/hooks.rb:326 1.912
After features/support/hooks.rb:100 0.000