Project Number Date
test_Tails_ISO_20522-ocr-more 13 22 Dec 2024, 05:13

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:18.316 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.253
Before features/support/hooks.rb:269 0.006
Given a computer 0.195
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 31.919
When I start Tails from USB drive "old" with network unplugged 1:27.969
Then the boot device has safe access rights 3.043
And Tails is running from USB drive "old" 0.342
And there is no persistence partition on USB drive "old" 0.088
And process "udev-watchdog" is running 0.089
And udev-watchdog is monitoring the correct device 0.310
And I unplug USB drive "old" 0.198
After features/support/hooks.rb:326 6.914
After features/support/hooks.rb:100 0.009
Tags: @product
2:8.560
Before features/support/hooks.rb:269 0.004
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login 1:23.862
Then Tails is running from USB drive "old" 0.357
And I create a persistent partition 33.702
And I take note of which tps features are available 1.379
Then a Tails persistence partition exists on USB drive "old" 0.818
And I shutdown Tails and wait for the computer to power off 8.254
After features/support/hooks.rb:326 0.167
After features/support/hooks.rb:100 0.008
Tags: @product
2:57.202
Before features/support/hooks.rb:269 0.005
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.177
Then Tails is running from USB drive "old" 1.985
And all tps features are active 3.145
When I write some files expected to persist 3.388
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.727
And all persistence configuration files have safe access rights 0.439
And all persistent directories from the old Tails version have safe access rights 3.951
And I take note of which tps features are available 0.522
And I shutdown Tails and wait for the computer to power off 4.347
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.333
After features/support/hooks.rb:326 0.137
After features/support/hooks.rb:100 0.010
Tags: @product
2:43.733
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 19.285
And I log in to a new session 23.073
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.529
And I plug USB drive "to_upgrade" 3.885
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.318
Then the running Tails is installed on USB drive "to_upgrade" 22.226
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.208
After features/support/hooks.rb:326 3.033
After features/support/hooks.rb:100 0.000
Tags: @product
2:7.810
Before features/support/hooks.rb:269 0.007
Given a computer 0.190
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:58.071
Then all tps features from the old Tails version are active 1.632
And Tails is running from USB drive "to_upgrade" 0.471
And the boot device has safe access rights 3.393
And the expected persistent files created with the old Tails version are present in the filesystem 1.607
And all persistent directories from the old Tails version have safe access rights 2.443
After features/support/hooks.rb:326 1.675
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:38.890
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.723
And no SquashFS delta is installed 0.228
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.508
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.083
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.520
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.428
When the network is plugged 0.079
And Tor is ready 23.578
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.408
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.259
Given I shutdown Tails and wait for the computer to power off 1:31.948
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.791
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.276
And the file system changes introduced in version 6.2~testoverlayfs are present 0.308
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.299
# 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.308
When the network is plugged 0.079
And Tor is ready 15.741
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.076
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.249
Given I shutdown Tails and wait for the computer to power off 4.463
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.497
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.364
And the file system changes introduced in version 6.3~testoverlayfs are present 0.630
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.304
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.434
When the network is plugged 0.066
And Tor is ready 19.126
Then the Upgrader considers the system as up-to-date 0.299
# 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.404
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.228
After features/support/hooks.rb:326 0.744
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
36.865
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 10.878
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.301
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.085
And the signing key used by the Upgrader is outdated 0.145
But a current signing key is available on our website 0.000
When the network is plugged 0.069
And Tor is ready 18.927
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.458
After features/support/hooks.rb:326 0.906
After features/support/hooks.rb:100 0.000