Project Number Date
test_Tails_ISO_20660-fix-random-seed-update 9 18 Nov 2024, 17:06

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:16.765 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:18.636
Before features/support/hooks.rb:269 0.006
Given a computer 0.203
And I create a 7200 MiB disk named "old" 0.054
And I plug USB drive "old" 1.061
And I write an old version of the Tails USB image to disk "old" 31.166
When I start Tails from USB drive "old" with network unplugged 1:41.846
Then the boot device has safe access rights 3.264
And Tails is running from USB drive "old" 0.329
And there is no persistence partition on USB drive "old" 0.081
And process "udev-watchdog" is running 0.106
And udev-watchdog is monitoring the correct device 0.311
And I unplug USB drive "old" 0.209
After features/support/hooks.rb:326 3.592
After features/support/hooks.rb:100 0.008
Tags: @product
2:9.695
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:23.571
Then Tails is running from USB drive "old" 0.317
And I create a persistent partition 32.408
And I take note of which tps features are available 1.632
Then a Tails persistence partition exists on USB drive "old" 1.238
And I shutdown Tails and wait for the computer to power off 10.336
After features/support/hooks.rb:326 0.139
After features/support/hooks.rb:100 0.022
Tags: @product
2:54.614
Before features/support/hooks.rb:269 0.012
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.780
Then Tails is running from USB drive "old" 1.164
And all tps features are active 2.017
When I write some files expected to persist 2.858
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.237
And all persistence configuration files have safe access rights 0.399
And all persistent directories from the old Tails version have safe access rights 2.420
And I take note of which tps features are available 0.502
And I shutdown Tails and wait for the computer to power off 4.686
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.351
After features/support/hooks.rb:326 0.137
After features/support/hooks.rb:100 0.008
Tags: @product
2:30.357
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 11.935
And I log in to a new session 20.117
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.694
And I plug USB drive "to_upgrade" 2.439
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.857
Then the running Tails is installed on USB drive "to_upgrade" 18.803
And I unplug USB drive "to_upgrade" 0.301
And I unplug USB drive "__internal" 0.208
After features/support/hooks.rb:326 0.978
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.315
Before features/support/hooks.rb:269 0.004
Given a computer 0.231
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.121
Then all tps features from the old Tails version are active 1.785
And Tails is running from USB drive "to_upgrade" 0.326
And the boot device has safe access rights 3.051
And the expected persistent files created with the old Tails version are present in the filesystem 1.456
And all persistent directories from the old Tails version have safe access rights 2.342
After features/support/hooks.rb:326 0.774
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:28.552
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.614
And no SquashFS delta is installed 0.096
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.512
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.333
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.492
When the network is plugged 0.078
And Tor is ready 18.827
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.706
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.515
Given I shutdown Tails and wait for the computer to power off 11.059
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.563
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 3.798
And the file system changes introduced in version 6.2~testoverlayfs are present 0.374
And only the 6.2~testoverlayfs SquashFS delta is installed 0.121
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.502
# 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.389
When the network is plugged 0.146
And Tor is ready 20.189
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.289
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.851
Given I shutdown Tails and wait for the computer to power off 4.325
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.990
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.055
And the file system changes introduced in version 6.3~testoverlayfs are present 0.501
And only the 6.3~testoverlayfs SquashFS delta is installed 0.061
# 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.580
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.321
When the network is plugged 0.079
And Tor is ready 17.945
Then the Upgrader considers the system as up-to-date 0.298
# 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.231
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.619
After features/support/hooks.rb:326 0.767
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
36.592
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 9.819
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.462
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.781
But a current signing key is available on our website 0.000
When the network is plugged 0.073
And Tor is ready 17.997
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.397
After features/support/hooks.rb:326 0.763
After features/support/hooks.rb:100 0.000