Project Number Date
test_Tails_ISO_stable 5101 18 Sep 2024, 19:39

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:26.351 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:11.018
Before features/support/hooks.rb:269 0.004
Given a computer 0.205
And I create a 7200 MiB disk named "old" 0.039
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 30.634
When I start Tails from USB drive "old" with network unplugged 1:34.986
Then the boot device has safe access rights 3.028
And Tails is running from USB drive "old" 0.337
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.286
And I unplug USB drive "old" 0.292
After features/support/hooks.rb:326 3.554
After features/support/hooks.rb:100 0.039
Tags: @product
2:11.476
Before features/support/hooks.rb:269 0.005
Given a computer 0.244
And I start Tails from USB drive "old" with network unplugged and I login 1:27.208
Then Tails is running from USB drive "old" 0.412
And I create a persistent partition 32.823
And I take note of which tps features are available 1.570
Then a Tails persistence partition exists on USB drive "old" 0.871
And I shutdown Tails and wait for the computer to power off 8.345
After features/support/hooks.rb:326 0.170
After features/support/hooks.rb:100 0.009
Tags: @product
2:56.735
Before features/support/hooks.rb:269 0.005
Given a computer 0.221
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.918
Then Tails is running from USB drive "old" 0.373
And all tps features are active 2.173
When I write some files expected to persist 1.954
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.300
And all persistence configuration files have safe access rights 0.418
And all persistent directories from the old Tails version have safe access rights 2.904
And I take note of which tps features are available 0.528
And I shutdown Tails and wait for the computer to power off 4.476
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.465
After features/support/hooks.rb:326 0.157
After features/support/hooks.rb:100 0.011
Tags: @product
2:42.444
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 13.310
And I log in to a new session 24.980
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.750
And I plug USB drive "to_upgrade" 4.263
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.591
Then the running Tails is installed on USB drive "to_upgrade" 21.037
And I unplug USB drive "to_upgrade" 0.276
And I unplug USB drive "__internal" 0.234
After features/support/hooks.rb:326 3.894
After features/support/hooks.rb:100 0.000
Tags: @product
2:25.260
Before features/support/hooks.rb:269 0.006
Given a computer 0.229
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.869
Then all tps features from the old Tails version are active 2.228
And Tails is running from USB drive "to_upgrade" 0.356
And the boot device has safe access rights 3.468
And the expected persistent files created with the old Tails version are present in the filesystem 1.487
And all persistent directories from the old Tails version have safe access rights 2.619
After features/support/hooks.rb:326 0.917
After features/support/hooks.rb:100 0.030
Tags: @product @automatic_upgrade
7:19.764
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 13.162
And no SquashFS delta is installed 0.102
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.377
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.380
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.487
When the network is plugged 0.079
And Tor is ready 19.635
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.524
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.297
Given I shutdown Tails and wait for the computer to power off 11.287
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:34.696
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.402
And the file system changes introduced in version 6.2~testoverlayfs are present 0.367
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.329
# 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.375
When the network is plugged 0.075
And Tor is ready 20.806
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.466
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.949
Given I shutdown Tails and wait for the computer to power off 4.470
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.336
Then Tails is running version 6.3~testoverlayfs 0.044
And all tps features are active 2.825
And the file system changes introduced in version 6.3~testoverlayfs are present 0.597
And only the 6.3~testoverlayfs SquashFS delta is installed 0.091
# 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.324
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.360
When the network is plugged 0.089
And Tor is ready 21.046
Then the Upgrader considers the system as up-to-date 0.351
# 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 17.110
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.152
After features/support/hooks.rb:326 0.811
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
39.653
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 11.024
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.326
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.726
But a current signing key is available on our website 0.000
When the network is plugged 0.064
And Tor is ready 20.320
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.134
After features/support/hooks.rb:326 0.698
After features/support/hooks.rb:100 0.000