Project Number Date
test_Tails_ISO_stable 5042 23 Aug 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 18:53.494 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:13.222
Before features/support/hooks.rb:269 0.007
Given a computer 0.191
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 29.539
When I start Tails from USB drive "old" with network unplugged 1:38.218
Then the boot device has safe access rights 3.162
And Tails is running from USB drive "old" 0.322
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.322
And I unplug USB drive "old" 0.181
After features/support/hooks.rb:326 7.544
After features/support/hooks.rb:100 0.012
Tags: @product
2:4.877
Before features/support/hooks.rb:269 0.007
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login 1:19.122
Then Tails is running from USB drive "old" 0.357
And I create a persistent partition 34.398
And I take note of which tps features are available 1.529
Then a Tails persistence partition exists on USB drive "old" 0.879
And I shutdown Tails and wait for the computer to power off 8.391
After features/support/hooks.rb:326 0.166
After features/support/hooks.rb:100 0.011
Tags: @product
2:48.979
Before features/support/hooks.rb:269 0.008
Given a computer 0.210
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.431
Then Tails is running from USB drive "old" 0.420
And all tps features are active 2.371
When I write some files expected to persist 1.727
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.213
And all persistence configuration files have safe access rights 0.532
And all persistent directories from the old Tails version have safe access rights 2.598
And I take note of which tps features are available 0.531
And I shutdown Tails and wait for the computer to power off 4.419
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.523
After features/support/hooks.rb:326 0.151
After features/support/hooks.rb:100 0.009
Tags: @product
2:26.436
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.373
And I log in to a new session 18.323
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.390
And I plug USB drive "to_upgrade" 2.465
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.474
Then the running Tails is installed on USB drive "to_upgrade" 19.988
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.216
After features/support/hooks.rb:326 3.488
After features/support/hooks.rb:100 0.000
Tags: @product
2:7.754
Before features/support/hooks.rb:269 0.007
Given a computer 0.219
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:58.682
Then all tps features from the old Tails version are active 1.576
And Tails is running from USB drive "to_upgrade" 0.321
And the boot device has safe access rights 3.102
And the expected persistent files created with the old Tails version are present in the filesystem 1.461
And all persistent directories from the old Tails version have safe access rights 2.390
After features/support/hooks.rb:326 0.581
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:33.698
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.925
And no SquashFS delta is installed 0.099
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.665
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.267
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.408
When the network is plugged 0.063
And Tor is ready 20.929
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.686
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.570
Given I shutdown Tails and wait for the computer to power off 10.574
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.094
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.509
And the file system changes introduced in version 6.2~testoverlayfs are present 0.392
And only the 6.2~testoverlayfs SquashFS delta is installed 0.076
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.344
# 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.256
When the network is plugged 0.083
And Tor is ready 21.182
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.233
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.226
Given I shutdown Tails and wait for the computer to power off 4.418
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.870
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.292
And the file system changes introduced in version 6.3~testoverlayfs are present 0.490
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.299
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.290
When the network is plugged 0.096
And Tor is ready 15.756
Then the Upgrader considers the system as up-to-date 10.892
# 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.526
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.993
After features/support/hooks.rb:326 0.751
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
38.524
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 13.863
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.835
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 1.089
But a current signing key is available on our website 0.000
When the network is plugged 0.095
And Tor is ready 17.172
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.401
After features/support/hooks.rb:326 0.686
After features/support/hooks.rb:100 0.000