Project Number Date
test_Tails_ISO_20660-fix-random-seed-update 6 15 Nov 2024, 17:26

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:18.381 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:8.748
Before features/support/hooks.rb:269 0.005
Given a computer 0.235
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.066
And I write an old version of the Tails USB image to disk "old" 31.696
When I start Tails from USB drive "old" with network unplugged 1:31.042
Then the boot device has safe access rights 3.526
And Tails is running from USB drive "old" 0.348
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.349
And I unplug USB drive "old" 0.263
After features/support/hooks.rb:326 7.222
After features/support/hooks.rb:100 0.010
Tags: @product
2:8.271
Before features/support/hooks.rb:269 0.005
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login 1:25.956
Then Tails is running from USB drive "old" 0.349
And I create a persistent partition 30.355
And I take note of which tps features are available 1.757
Then a Tails persistence partition exists on USB drive "old" 0.831
And I shutdown Tails and wait for the computer to power off 8.829
After features/support/hooks.rb:326 0.167
After features/support/hooks.rb:100 0.008
Tags: @product
2:56.729
Before features/support/hooks.rb:269 0.004
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.673
Then Tails is running from USB drive "old" 0.367
And all tps features are active 2.110
When I write some files expected to persist 1.973
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.264
And all persistence configuration files have safe access rights 0.430
And all persistent directories from the old Tails version have safe access rights 2.551
And I take note of which tps features are available 0.493
And I shutdown Tails and wait for the computer to power off 4.169
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.506
After features/support/hooks.rb:326 0.141
After features/support/hooks.rb:100 0.009
Tags: @product
2:31.220
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.605
And I log in to a new session 18.299
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.725
And I plug USB drive "to_upgrade" 2.395
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.550
Then the running Tails is installed on USB drive "to_upgrade" 21.266
And I unplug USB drive "to_upgrade" 0.192
And I unplug USB drive "__internal" 0.184
After features/support/hooks.rb:326 6.945
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.181
Before features/support/hooks.rb:269 0.007
Given a computer 0.247
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.821
Then all tps features from the old Tails version are active 1.622
And Tails is running from USB drive "to_upgrade" 0.360
And the boot device has safe access rights 3.278
And the expected persistent files created with the old Tails version are present in the filesystem 1.643
And all persistent directories from the old Tails version have safe access rights 3.208
After features/support/hooks.rb:326 0.653
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:37.242
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 12.420
And no SquashFS delta is installed 0.889
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.327
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.294
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.535
When the network is plugged 0.132
And Tor is ready 23.716
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.579
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.274
Given I shutdown Tails and wait for the computer to power off 8.624
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.328
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.412
And the file system changes introduced in version 6.2~testoverlayfs are present 0.289
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.308
# 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.259
When the network is plugged 0.089
And Tor is ready 17.591
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.358
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.048
Given I shutdown Tails and wait for the computer to power off 4.555
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.495
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.477
And the file system changes introduced in version 6.3~testoverlayfs are present 0.564
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.340
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.323
When the network is plugged 0.134
And Tor is ready 19.671
Then the Upgrader considers the system as up-to-date 0.320
# 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.710
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.930
After features/support/hooks.rb:326 0.832
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
35.988
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 10.827
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.311
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the signing key used by the Upgrader is outdated 0.812
But a current signing key is available on our website 0.000
When the network is plugged 0.077
And Tor is ready 17.663
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.227
After features/support/hooks.rb:326 0.717
After features/support/hooks.rb:100 0.000