Project Number Date
test_Tails_ISO_20660-fix-random-seed-update 1 11 Nov 2024, 03:32

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 18:44.527 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
1:58.811
Before features/support/hooks.rb:269 0.005
Given a computer 0.226
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.062
And I write an old version of the Tails USB image to disk "old" 29.163
When I start Tails from USB drive "old" with network unplugged 1:24.055
Then the boot device has safe access rights 3.207
And Tails is running from USB drive "old" 0.362
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.325
And I unplug USB drive "old" 0.195
After features/support/hooks.rb:326 3.728
After features/support/hooks.rb:100 0.009
Tags: @product
2:3.257
Before features/support/hooks.rb:269 0.007
Given a computer 0.237
And I start Tails from USB drive "old" with network unplugged and I login 1:20.811
Then Tails is running from USB drive "old" 0.362
And I create a persistent partition 30.973
And I take note of which tps features are available 1.515
Then a Tails persistence partition exists on USB drive "old" 0.888
And I shutdown Tails and wait for the computer to power off 8.467
After features/support/hooks.rb:326 0.201
After features/support/hooks.rb:100 0.007
Tags: @product
2:50.274
Before features/support/hooks.rb:269 0.004
Given a computer 0.242
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.494
Then Tails is running from USB drive "old" 1.210
And all tps features are active 2.089
When I write some files expected to persist 1.672
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.211
And all persistence configuration files have safe access rights 0.374
And all persistent directories from the old Tails version have safe access rights 3.346
And I take note of which tps features are available 0.443
And I shutdown Tails and wait for the computer to power off 4.286
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.902
After features/support/hooks.rb:326 0.131
After features/support/hooks.rb:100 0.009
Tags: @product
2:33.434
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.367
And I log in to a new session 21.890
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.405
And I plug USB drive "to_upgrade" 2.453
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.290
Then the running Tails is installed on USB drive "to_upgrade" 22.632
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.191
After features/support/hooks.rb:326 2.164
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.135
Before features/support/hooks.rb:269 0.006
Given a computer 0.188
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.436
Then all tps features from the old Tails version are active 1.551
And Tails is running from USB drive "to_upgrade" 0.405
And the boot device has safe access rights 3.130
And the expected persistent files created with the old Tails version are present in the filesystem 1.389
And all persistent directories from the old Tails version have safe access rights 3.035
After features/support/hooks.rb:326 0.742
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
6:31.228
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 12.821
And no SquashFS delta is installed 0.230
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.415
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.094
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.336
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.579
When the network is plugged 0.113
And Tor is ready 22.209
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.507
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.109
Given I shutdown Tails and wait for the computer to power off 15.577
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.095
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.188
And the file system changes introduced in version 6.2~testoverlayfs are present 0.275
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.373
# 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.300
When the network is plugged 0.072
And Tor is ready 16.804
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.398
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.337
Given I shutdown Tails and wait for the computer to power off 4.324
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.880
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.030
And the file system changes introduced in version 6.3~testoverlayfs are present 0.538
And only the 6.3~testoverlayfs SquashFS delta is installed 0.064
# 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.407
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.252
When the network is plugged 0.089
And Tor is ready 17.125
Then the Upgrader considers the system as up-to-date 0.314
# 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.271
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.991
After features/support/hooks.rb:326 0.749
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
35.385
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 10.070
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.469
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.902
But a current signing key is available on our website 0.000
When the network is plugged 0.086
And Tor is ready 18.844
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.954
After features/support/hooks.rb:326 0.671
After features/support/hooks.rb:100 0.000