Project Number Date
test_Tails_ISO_20660-fix-random-seed-update 7 16 Nov 2024, 17:25

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:51.127 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:17.211
Before features/support/hooks.rb:269 0.004
Given a computer 1.025
And I create a 7200 MiB disk named "old" 0.390
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 33.804
When I start Tails from USB drive "old" with network unplugged 1:36.077
Then the boot device has safe access rights 3.632
And Tails is running from USB drive "old" 0.492
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.348
And I unplug USB drive "old" 0.206
After features/support/hooks.rb:326 3.826
After features/support/hooks.rb:100 0.011
Tags: @product
2:23.108
Before features/support/hooks.rb:269 0.005
Given a computer 0.242
And I start Tails from USB drive "old" with network unplugged and I login 1:36.811
Then Tails is running from USB drive "old" 0.353
And I create a persistent partition 34.059
And I take note of which tps features are available 2.056
Then a Tails persistence partition exists on USB drive "old" 0.881
And I shutdown Tails and wait for the computer to power off 8.705
After features/support/hooks.rb:326 0.184
After features/support/hooks.rb:100 0.010
Tags: @product
2:58.473
Before features/support/hooks.rb:269 0.005
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.845
Then Tails is running from USB drive "old" 0.492
And all tps features are active 1.962
When I write some files expected to persist 1.818
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.235
And all persistence configuration files have safe access rights 0.420
And all persistent directories from the old Tails version have safe access rights 3.170
And I take note of which tps features are available 0.425
And I shutdown Tails and wait for the computer to power off 4.416
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.498
After features/support/hooks.rb:326 0.162
After features/support/hooks.rb:100 0.008
Tags: @product
2:32.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.900
And I log in to a new session 20.862
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.822
And I plug USB drive "to_upgrade" 2.456
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.163
Then the running Tails is installed on USB drive "to_upgrade" 19.185
And I unplug USB drive "to_upgrade" 0.285
And I unplug USB drive "__internal" 0.202
After features/support/hooks.rb:326 3.993
After features/support/hooks.rb:100 0.000
Tags: @product
2:23.187
Before features/support/hooks.rb:269 0.006
Given a computer 0.447
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.818
Then all tps features from the old Tails version are active 1.767
And Tails is running from USB drive "to_upgrade" 0.389
And the boot device has safe access rights 3.598
And the expected persistent files created with the old Tails version are present in the filesystem 1.551
And all persistent directories from the old Tails version have safe access rights 2.613
After features/support/hooks.rb:326 0.805
After features/support/hooks.rb:100 0.009
7:41.797
Before features/support/hooks.rb:269 0.013
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.780
And no SquashFS delta is installed 0.115
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.405
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.302
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.418
When the network is plugged 0.070
And Tor is ready 49.630
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.593
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.679
Given I shutdown Tails and wait for the computer to power off 11.434
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.858
Then Tails is running version 6.2~testoverlayfs 0.032
And all tps features are active 2.500
And the file system changes introduced in version 6.2~testoverlayfs are present 0.322
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.341
# 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.328
When the network is plugged 0.087
And Tor is ready 17.426
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.956
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.301
Given I shutdown Tails and wait for the computer to power off 58.995
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.221
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.961
And the file system changes introduced in version 6.3~testoverlayfs are present 0.512
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.336
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.285
When the network is plugged 0.069
And Tor is ready 19.123
Then the Upgrader considers the system as up-to-date 0.339
# 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 15.182
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.964
After features/support/hooks.rb:326 0.883
After features/support/hooks.rb:100 0.033
34.469
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 10.196
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.352
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 0.763
But a current signing key is available on our website 0.000
When the network is plugged 0.101
And Tor is ready 16.292
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.697
After features/support/hooks.rb:326 1.321
After features/support/hooks.rb:100 0.000