Project Number Date
test_Tails_ISO_stable 4902 18 Jun 2024, 21:01

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 19:24.066 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:23.527
Before features/support/hooks.rb:269 0.006
Given a computer 0.241
And I create a 7200 MiB disk named "old" 0.056
And I plug USB drive "old" 1.067
And I write an old version of the Tails USB image to disk "old" 30.463
When I start Tails from USB drive "old" with network unplugged 1:47.578
Then the boot device has safe access rights 3.127
And Tails is running from USB drive "old" 0.363
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.085
And udev-watchdog is monitoring the correct device 0.292
And I unplug USB drive "old" 0.184
After features/support/hooks.rb:326 7.547
After features/support/hooks.rb:100 0.013
Tags: @product
2:12.166
Before features/support/hooks.rb:269 0.007
Given a computer 0.239
And I start Tails from USB drive "old" with network unplugged and I login 1:28.520
Then Tails is running from USB drive "old" 0.356
And I create a persistent partition 31.434
And I take note of which tps features are available 1.756
Then a Tails persistence partition exists on USB drive "old" 0.977
And I shutdown Tails and wait for the computer to power off 8.882
After features/support/hooks.rb:326 0.172
After features/support/hooks.rb:100 0.011
Tags: @product
2:59.176
Before features/support/hooks.rb:269 0.011
Given a computer 0.265
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.685
Then Tails is running from USB drive "old" 0.402
And all tps features are active 2.886
When I write some files expected to persist 1.964
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.244
And all persistence configuration files have safe access rights 0.409
And all persistent directories from the old Tails version have safe access rights 2.523
And I take note of which tps features are available 0.495
And I shutdown Tails and wait for the computer to power off 4.498
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.802
After features/support/hooks.rb:326 0.092
After features/support/hooks.rb:100 0.010
Tags: @product
2:27.002
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.817
And I log in to a new session 19.718
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.759
And I plug USB drive "to_upgrade" 2.448
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.540
Then the running Tails is installed on USB drive "to_upgrade" 18.211
And I unplug USB drive "to_upgrade" 0.256
And I unplug USB drive "__internal" 0.251
After features/support/hooks.rb:326 3.514
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.620
Before features/support/hooks.rb:269 0.008
Given a computer 0.215
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.983
Then all tps features from the old Tails version are active 1.605
And Tails is running from USB drive "to_upgrade" 0.357
And the boot device has safe access rights 3.573
And the expected persistent files created with the old Tails version are present in the filesystem 1.440
And all persistent directories from the old Tails version have safe access rights 2.445
After features/support/hooks.rb:326 0.990
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:30.054
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.431
And no SquashFS delta is installed 0.114
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.278
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.342
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.472
When the network is plugged 0.223
And Tor is ready 23.763
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.338
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.621
Given I shutdown Tails and wait for the computer to power off 8.870
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.514
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.493
And the file system changes introduced in version 6.2~testoverlayfs are present 0.351
And only the 6.2~testoverlayfs SquashFS delta is installed 0.084
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.358
# 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.286
When the network is plugged 0.048
And Tor is ready 18.280
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.460
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.338
Given I shutdown Tails and wait for the computer to power off 4.428
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.128
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.055
And the file system changes introduced in version 6.3~testoverlayfs are present 0.567
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.311
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.264
When the network is plugged 0.037
And Tor is ready 17.741
Then the Upgrader considers the system as up-to-date 0.324
# 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.440
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.931
After features/support/hooks.rb:326 0.747
After features/support/hooks.rb:100 0.029
Tags: @product @automatic_upgrade
34.517
Before features/support/hooks.rb:269 0.024
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.776
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.462
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 0.746
But a current signing key is available on our website 0.000
When the network is plugged 0.036
And Tor is ready 18.385
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.061
After features/support/hooks.rb:326 0.682
After features/support/hooks.rb:100 0.000