Project Number Date
test_Tails_ISO_stable 5088 10 Sep 2024, 08:40

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:19.777 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:9.204
Before features/support/hooks.rb:269 0.005
Given a computer 0.221
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 27.778
When I start Tails from USB drive "old" with network unplugged 1:35.885
Then the boot device has safe access rights 3.146
And Tails is running from USB drive "old" 0.373
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.087
And udev-watchdog is monitoring the correct device 0.326
And I unplug USB drive "old" 0.202
After features/support/hooks.rb:326 3.529
After features/support/hooks.rb:100 0.007
Tags: @product
2:9.560
Before features/support/hooks.rb:269 0.005
Given a computer 0.255
And I start Tails from USB drive "old" with network unplugged and I login 1:24.177
Then Tails is running from USB drive "old" 0.389
And I create a persistent partition 33.471
And I take note of which tps features are available 1.542
Then a Tails persistence partition exists on USB drive "old" 0.903
And I shutdown Tails and wait for the computer to power off 8.821
After features/support/hooks.rb:326 0.181
After features/support/hooks.rb:100 0.009
Tags: @product
3:2.476
Before features/support/hooks.rb:269 0.005
Given a computer 0.205
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.338
Then Tails is running from USB drive "old" 0.420
And all tps features are active 2.085
When I write some files expected to persist 1.756
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.209
And all persistence configuration files have safe access rights 0.392
And all persistent directories from the old Tails version have safe access rights 3.016
And I take note of which tps features are available 0.450
And I shutdown Tails and wait for the computer to power off 4.386
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.215
After features/support/hooks.rb:326 0.159
After features/support/hooks.rb:100 0.009
Tags: @product
2:42.069
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.819
And I log in to a new session 25.948
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.684
And I plug USB drive "to_upgrade" 2.474
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.887
Then the running Tails is installed on USB drive "to_upgrade" 22.828
And I unplug USB drive "to_upgrade" 0.215
And I unplug USB drive "__internal" 0.210
After features/support/hooks.rb:326 2.046
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.135
Before features/support/hooks.rb:269 0.007
Given a computer 0.201
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.918
Then all tps features from the old Tails version are active 2.061
And Tails is running from USB drive "to_upgrade" 0.398
And the boot device has safe access rights 3.581
And the expected persistent files created with the old Tails version are present in the filesystem 1.426
And all persistent directories from the old Tails version have safe access rights 2.547
After features/support/hooks.rb:326 0.869
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:58.147
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 14.278
And no SquashFS delta is installed 0.326
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.380
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.407
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.517
When the network is plugged 0.307
And Tor is ready 48.948
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.601
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.709
Given I shutdown Tails and wait for the computer to power off 8.808
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.477
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.322
And the file system changes introduced in version 6.2~testoverlayfs are present 0.293
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.305
# 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.257
When the network is plugged 0.082
And Tor is ready 20.574
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.519
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.698
Given I shutdown Tails and wait for the computer to power off 4.315
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.069
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.302
And the file system changes introduced in version 6.3~testoverlayfs are present 0.538
And only the 6.3~testoverlayfs SquashFS delta is installed 0.087
# 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.312
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.307
When the network is plugged 0.077
And Tor is ready 18.916
Then the Upgrader considers the system as up-to-date 0.410
# 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.727
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.073
After features/support/hooks.rb:326 0.754
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
58.184
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.803
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.325
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.076
And the signing key used by the Upgrader is outdated 0.926
But a current signing key is available on our website 0.000
When the network is plugged 0.081
And Tor is ready 46.380
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.590
After features/support/hooks.rb:326 0.891
After features/support/hooks.rb:100 0.000