Project Number Date
test_Tails_ISO_stable 5280 20 Nov 2024, 21:34

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:21.706 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:6.322
Before features/support/hooks.rb:269 0.006
Given a computer 0.223
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 32.419
When I start Tails from USB drive "old" with network unplugged 1:28.262
Then the boot device has safe access rights 3.265
And Tails is running from USB drive "old" 0.329
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.304
And I unplug USB drive "old" 0.256
After features/support/hooks.rb:326 3.552
After features/support/hooks.rb:100 0.010
Tags: @product
2:9.550
Before features/support/hooks.rb:269 0.007
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login 1:25.231
Then Tails is running from USB drive "old" 0.323
And I create a persistent partition 34.777
And I take note of which tps features are available 1.715
Then a Tails persistence partition exists on USB drive "old" 0.844
And I shutdown Tails and wait for the computer to power off 6.460
After features/support/hooks.rb:326 0.206
After features/support/hooks.rb:100 0.011
Tags: @product
2:53.142
Before features/support/hooks.rb:269 0.004
Given a computer 0.193
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.540
Then Tails is running from USB drive "old" 0.449
And all tps features are active 1.927
When I write some files expected to persist 1.759
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.229
And all persistence configuration files have safe access rights 0.413
And all persistent directories from the old Tails version have safe access rights 2.783
And I take note of which tps features are available 0.470
And I shutdown Tails and wait for the computer to power off 4.403
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.970
After features/support/hooks.rb:326 0.147
After features/support/hooks.rb:100 0.010
Tags: @product
2:33.878
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 11.139
And I log in to a new session 19.963
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.138
And I plug USB drive "to_upgrade" 2.367
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.124
Then the running Tails is installed on USB drive "to_upgrade" 23.732
And I unplug USB drive "to_upgrade" 0.210
And I unplug USB drive "__internal" 0.202
After features/support/hooks.rb:326 2.327
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.722
Before features/support/hooks.rb:269 0.007
Given a computer 0.725
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.805
Then all tps features from the old Tails version are active 1.672
And Tails is running from USB drive "to_upgrade" 0.315
And the boot device has safe access rights 3.089
And the expected persistent files created with the old Tails version are present in the filesystem 1.638
And all persistent directories from the old Tails version have safe access rights 2.476
After features/support/hooks.rb:326 0.794
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:39.855
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.429
And no SquashFS delta is installed 0.089
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.486
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.162
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.298
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.438
When the network is plugged 0.063
And Tor is ready 21.830
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.872
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.543
Given I shutdown Tails and wait for the computer to power off 10.849
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.012
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 1.996
And the file system changes introduced in version 6.2~testoverlayfs are present 0.292
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.319
# 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.262
When the network is plugged 0.067
And Tor is ready 20.610
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.974
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 12.458
Given I shutdown Tails and wait for the computer to power off 4.392
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.754
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.120
And the file system changes introduced in version 6.3~testoverlayfs are present 0.635
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.308
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.293
When the network is plugged 0.057
And Tor is ready 18.178
Then the Upgrader considers the system as up-to-date 0.337
# 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.388
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.151
After features/support/hooks.rb:326 0.705
After features/support/hooks.rb:100 0.038
Tags: @product @automatic_upgrade
39.235
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.608
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.708
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.092
And the signing key used by the Upgrader is outdated 0.889
But a current signing key is available on our website 0.000
When the network is plugged 0.092
And Tor is ready 21.539
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.305
After features/support/hooks.rb:326 0.753
After features/support/hooks.rb:100 0.000