Project Number Date
test_Tails_ISO_20522-ocr-more 25 03 Jan 2025, 05:05

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:9.457 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:5.840
Before features/support/hooks.rb:269 0.005
Given a computer 0.184
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.059
And I write an old version of the Tails USB image to disk "old" 31.651
When I start Tails from USB drive "old" with network unplugged 1:28.395
Then the boot device has safe access rights 3.361
And Tails is running from USB drive "old" 0.384
And there is no persistence partition on USB drive "old" 0.084
And process "udev-watchdog" is running 0.120
And udev-watchdog is monitoring the correct device 0.325
And I unplug USB drive "old" 0.230
After features/support/hooks.rb:326 3.539
After features/support/hooks.rb:100 0.033
Tags: @product
2:6.743
Before features/support/hooks.rb:269 0.005
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login 1:21.507
Then Tails is running from USB drive "old" 0.319
And I create a persistent partition 33.467
And I take note of which tps features are available 1.826
Then a Tails persistence partition exists on USB drive "old" 0.879
And I shutdown Tails and wait for the computer to power off 8.561
After features/support/hooks.rb:326 0.184
After features/support/hooks.rb:100 0.008
Tags: @product
2:52.413
Before features/support/hooks.rb:269 0.005
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.474
Then Tails is running from USB drive "old" 0.359
And all tps features are active 1.893
When I write some files expected to persist 2.076
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.221
And all persistence configuration files have safe access rights 0.379
And all persistent directories from the old Tails version have safe access rights 2.436
And I take note of which tps features are available 0.454
And I shutdown Tails and wait for the computer to power off 4.226
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.700
After features/support/hooks.rb:326 0.119
After features/support/hooks.rb:100 0.009
Tags: @product
2:40.369
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 15.702
And I log in to a new session 20.250
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.619
And I plug USB drive "to_upgrade" 4.410
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.386
Then the running Tails is installed on USB drive "to_upgrade" 22.569
And I unplug USB drive "to_upgrade" 0.209
And I unplug USB drive "__internal" 0.220
After features/support/hooks.rb:326 7.578
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.282
Before features/support/hooks.rb:269 0.006
Given a computer 0.178
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.367
Then all tps features from the old Tails version are active 1.996
And Tails is running from USB drive "to_upgrade" 0.373
And the boot device has safe access rights 3.430
And the expected persistent files created with the old Tails version are present in the filesystem 1.460
And all persistent directories from the old Tails version have safe access rights 2.475
After features/support/hooks.rb:326 1.232
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:36.475
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 13.732
And no SquashFS delta is installed 0.111
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.419
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.108
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.376
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.518
When the network is plugged 0.084
And Tor is ready 23.518
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.821
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.727
Given I shutdown Tails and wait for the computer to power off 11.171
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.396
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 2.320
And the file system changes introduced in version 6.2~testoverlayfs are present 0.318
And only the 6.2~testoverlayfs SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.405
# 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.937
When the network is plugged 0.076
And Tor is ready 15.966
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.543
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.174
Given I shutdown Tails and wait for the computer to power off 4.356
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.207
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.263
And the file system changes introduced in version 6.3~testoverlayfs are present 0.601
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.319
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.438
When the network is plugged 0.122
And Tor is ready 16.530
Then the Upgrader considers the system as up-to-date 10.910
# 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 17.910
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.907
After features/support/hooks.rb:326 0.750
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
34.331
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.042
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.418
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 0.075
But a current signing key is available on our website 0.000
When the network is plugged 0.062
And Tor is ready 18.833
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.835
After features/support/hooks.rb:326 0.739
After features/support/hooks.rb:100 0.000