Project Number Date
test_Tails_ISO_20660-fix-random-seed-update 10 19 Nov 2024, 16:43

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:20.290 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:2.028
Before features/support/hooks.rb:269 0.005
Given a computer 0.176
And I create a 7200 MiB disk named "old" 0.039
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 30.463
When I start Tails from USB drive "old" with network unplugged 1:26.343
Then the boot device has safe access rights 2.984
And Tails is running from USB drive "old" 0.313
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.112
And udev-watchdog is monitoring the correct device 0.289
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:326 7.063
After features/support/hooks.rb:100 0.009
Tags: @product
2:1.290
Before features/support/hooks.rb:269 0.005
Given a computer 0.177
And I start Tails from USB drive "old" with network unplugged and I login 1:23.378
Then Tails is running from USB drive "old" 0.326
And I create a persistent partition 28.593
And I take note of which tps features are available 1.600
Then a Tails persistence partition exists on USB drive "old" 0.731
And I shutdown Tails and wait for the computer to power off 6.482
After features/support/hooks.rb:326 0.146
After features/support/hooks.rb:100 0.009
Tags: @product
2:42.421
Before features/support/hooks.rb:269 0.006
Given a computer 0.179
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:5.971
Then Tails is running from USB drive "old" 0.662
And all tps features are active 1.861
When I write some files expected to persist 1.669
# 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.420
And all persistent directories from the old Tails version have safe access rights 2.401
And I take note of which tps features are available 0.506
And I shutdown Tails and wait for the computer to power off 4.320
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.216
After features/support/hooks.rb:326 0.119
After features/support/hooks.rb:100 0.009
Tags: @product
2:26.122
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.262
And I log in to a new session 18.073
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.915
And I plug USB drive "to_upgrade" 2.386
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.646
Then the running Tails is installed on USB drive "to_upgrade" 19.410
And I unplug USB drive "to_upgrade" 0.243
And I unplug USB drive "__internal" 0.183
After features/support/hooks.rb:326 2.079
After features/support/hooks.rb:100 0.000
Tags: @product
2:11.107
Before features/support/hooks.rb:269 0.006
Given a computer 0.183
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.208
Then all tps features from the old Tails version are active 1.507
And Tails is running from USB drive "to_upgrade" 0.341
And the boot device has safe access rights 3.090
And the expected persistent files created with the old Tails version are present in the filesystem 1.407
And all persistent directories from the old Tails version have safe access rights 2.367
After features/support/hooks.rb:326 0.691
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:20.331
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 11.385
And no SquashFS delta is installed 0.131
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.398
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.317
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.444
When the network is plugged 0.065
And Tor is ready 18.971
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.450
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.196
Given I shutdown Tails and wait for the computer to power off 8.434
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.903
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.072
And the file system changes introduced in version 6.2~testoverlayfs are present 0.286
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.320
# 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.248
When the network is plugged 0.074
And Tor is ready 19.467
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.220
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.720
Given I shutdown Tails and wait for the computer to power off 4.270
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.753
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.937
And the file system changes introduced in version 6.3~testoverlayfs are present 0.634
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.314
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.268
When the network is plugged 0.083
And Tor is ready 18.200
Then the Upgrader considers the system as up-to-date 0.302
# 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.173
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.053
After features/support/hooks.rb:326 0.682
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
36.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 9.934
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.363
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.852
But a current signing key is available on our website 0.000
When the network is plugged 0.069
And Tor is ready 19.217
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.493
After features/support/hooks.rb:326 0.677
After features/support/hooks.rb:100 0.000