Project Number Date
test_Tails_ISO_stable 5063 01 Sep 2024, 12:23

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:48.608 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:7.444
Before features/support/hooks.rb:269 0.007
Given a computer 0.190
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 29.095
When I start Tails from USB drive "old" with network unplugged 1:33.205
Then the boot device has safe access rights 2.899
And Tails is running from USB drive "old" 0.320
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.085
And udev-watchdog is monitoring the correct device 0.294
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:326 6.976
After features/support/hooks.rb:100 0.009
Tags: @product
2:0.775
Before features/support/hooks.rb:269 0.006
Given a computer 0.207
And I start Tails from USB drive "old" with network unplugged and I login 1:18.337
Then Tails is running from USB drive "old" 0.294
And I create a persistent partition 30.986
And I take note of which tps features are available 1.471
Then a Tails persistence partition exists on USB drive "old" 0.779
And I shutdown Tails and wait for the computer to power off 8.697
After features/support/hooks.rb:326 0.140
After features/support/hooks.rb:100 0.021
Tags: @product
2:48.382
Before features/support/hooks.rb:269 0.006
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.113
Then Tails is running from USB drive "old" 0.333
And all tps features are active 1.886
When I write some files expected to persist 1.519
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.259
And all persistence configuration files have safe access rights 0.446
And all persistent directories from the old Tails version have safe access rights 2.546
And I take note of which tps features are available 0.497
And I shutdown Tails and wait for the computer to power off 4.287
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.296
After features/support/hooks.rb:326 0.139
After features/support/hooks.rb:100 0.009
Tags: @product
2:26.863
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.725
And I log in to a new session 17.231
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.448
And I plug USB drive "to_upgrade" 2.374
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.184
Then the running Tails is installed on USB drive "to_upgrade" 21.424
And I unplug USB drive "to_upgrade" 0.211
And I unplug USB drive "__internal" 0.261
After features/support/hooks.rb:326 2.222
After features/support/hooks.rb:100 0.000
Tags: @product
2:6.119
Before features/support/hooks.rb:269 0.007
Given a computer 0.192
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:57.155
Then all tps features from the old Tails version are active 1.578
And Tails is running from USB drive "to_upgrade" 0.336
And the boot device has safe access rights 2.980
And the expected persistent files created with the old Tails version are present in the filesystem 1.582
And all persistent directories from the old Tails version have safe access rights 2.293
After features/support/hooks.rb:326 0.578
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:42.809
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.286
And no SquashFS delta is installed 0.129
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.250
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.260
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.481
When the network is plugged 0.085
And Tor is ready 18.666
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.865
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.655
Given I shutdown Tails and wait for the computer to power off 8.507
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.521
Then Tails is running version 6.2~testoverlayfs 0.034
And all tps features are active 2.256
And the file system changes introduced in version 6.2~testoverlayfs are present 0.339
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.326
# 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.269
When the network is plugged 0.073
And Tor is ready 44.876
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.557
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.987
Given I shutdown Tails and wait for the computer to power off 4.188
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.414
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.003
And the file system changes introduced in version 6.3~testoverlayfs are present 0.459
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.314
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.256
When the network is plugged 0.080
And Tor is ready 16.102
Then the Upgrader considers the system as up-to-date 10.747
# 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.749
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.850
After features/support/hooks.rb:326 0.678
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
36.213
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 9.594
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.263
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the signing key used by the Upgrader is outdated 0.736
But a current signing key is available on our website 0.000
When the network is plugged 0.090
And Tor is ready 18.921
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.558
After features/support/hooks.rb:326 0.659
After features/support/hooks.rb:100 0.000