Project Number Date
test_Tails_ISO_20660-fix-random-seed-update 5 14 Nov 2024, 17:11

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:32.166 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:21.186
Before features/support/hooks.rb:269 0.004
Given a computer 0.178
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 27.615
When I start Tails from USB drive "old" with network unplugged 1:48.238
Then the boot device has safe access rights 3.057
And Tails is running from USB drive "old" 0.326
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.332
And I unplug USB drive "old" 0.190
After features/support/hooks.rb:326 7.267
After features/support/hooks.rb:100 0.007
Tags: @product
2:9.896
Before features/support/hooks.rb:269 0.005
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login 1:29.516
Then Tails is running from USB drive "old" 0.309
And I create a persistent partition 31.253
And I take note of which tps features are available 1.424
Then a Tails persistence partition exists on USB drive "old" 0.878
And I shutdown Tails and wait for the computer to power off 6.309
After features/support/hooks.rb:326 0.193
After features/support/hooks.rb:100 0.009
Tags: @product
2:51.360
Before features/support/hooks.rb:269 0.005
Given a computer 0.264
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.702
Then Tails is running from USB drive "old" 0.524
And all tps features are active 1.970
When I write some files expected to persist 1.622
# 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.385
And all persistent directories from the old Tails version have safe access rights 2.682
And I take note of which tps features are available 0.472
And I shutdown Tails and wait for the computer to power off 4.288
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.217
After features/support/hooks.rb:326 0.114
After features/support/hooks.rb:100 0.009
Tags: @product
2:30.447
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.916
And I log in to a new session 22.677
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.600
And I plug USB drive "to_upgrade" 2.480
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.878
Then the running Tails is installed on USB drive "to_upgrade" 18.515
And I unplug USB drive "to_upgrade" 0.194
And I unplug USB drive "__internal" 0.183
After features/support/hooks.rb:326 1.241
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.916
Before features/support/hooks.rb:269 0.006
Given a computer 0.185
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.565
Then all tps features from the old Tails version are active 1.629
And Tails is running from USB drive "to_upgrade" 0.318
And the boot device has safe access rights 3.438
And the expected persistent files created with the old Tails version are present in the filesystem 1.481
And all persistent directories from the old Tails version have safe access rights 2.297
After features/support/hooks.rb:326 0.722
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:39.717
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 15.171
And no SquashFS delta is installed 1.489
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.303
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.328
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.495
When the network is plugged 0.065
And Tor is ready 27.369
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.519
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.606
Given I shutdown Tails and wait for the computer to power off 10.754
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.616
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.159
And the file system changes introduced in version 6.2~testoverlayfs are present 0.348
And only the 6.2~testoverlayfs SquashFS delta is installed 0.114
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.310
# 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.342
When the network is plugged 0.076
And Tor is ready 20.732
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.045
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.674
Given I shutdown Tails and wait for the computer to power off 4.326
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.134
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.085
And the file system changes introduced in version 6.3~testoverlayfs are present 0.491
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.350
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.495
When the network is plugged 0.228
And Tor is ready 18.942
Then the Upgrader considers the system as up-to-date 0.324
# 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.724
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.941
After features/support/hooks.rb:326 0.958
After features/support/hooks.rb:100 0.056
Tags: @product @automatic_upgrade
44.641
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 14.546
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.335
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.084
And the signing key used by the Upgrader is outdated 1.052
But a current signing key is available on our website 0.000
When the network is plugged 0.076
And Tor is ready 21.651
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.894
After features/support/hooks.rb:326 1.720
After features/support/hooks.rb:100 0.000