Project Number Date
test_Tails_ISO_20530-tca-controls-tor-flag-file 10 07 Nov 2024, 20:53

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:39.071 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.204
Before features/support/hooks.rb:269 0.005
Given a computer 0.185
And I create a 7200 MiB disk named "old" 0.058
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 31.307
When I start Tails from USB drive "old" with network unplugged 1:27.659
Then the boot device has safe access rights 3.769
And Tails is running from USB drive "old" 0.399
And there is no persistence partition on USB drive "old" 0.084
And process "udev-watchdog" is running 0.106
And udev-watchdog is monitoring the correct device 0.364
And I unplug USB drive "old" 0.215
After features/support/hooks.rb:326 7.897
After features/support/hooks.rb:100 0.009
Tags: @product
2:11.587
Before features/support/hooks.rb:269 0.004
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login 1:26.480
Then Tails is running from USB drive "old" 0.390
And I create a persistent partition 33.227
And I take note of which tps features are available 2.174
Then a Tails persistence partition exists on USB drive "old" 0.805
And I shutdown Tails and wait for the computer to power off 8.300
After features/support/hooks.rb:326 0.232
After features/support/hooks.rb:100 0.009
Tags: @product
2:46.226
Before features/support/hooks.rb:269 0.005
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:8.835
Then Tails is running from USB drive "old" 0.809
And all tps features are active 1.902
When I write some files expected to persist 1.725
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.193
And all persistence configuration files have safe access rights 0.443
And all persistent directories from the old Tails version have safe access rights 2.893
And I take note of which tps features are available 0.412
And I shutdown Tails and wait for the computer to power off 4.355
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.464
After features/support/hooks.rb:326 0.121
After features/support/hooks.rb:100 0.007
Tags: @product
2:36.366
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 11.446
And I log in to a new session 20.819
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.670
And I plug USB drive "to_upgrade" 2.457
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.907
Then the running Tails is installed on USB drive "to_upgrade" 19.646
And I unplug USB drive "to_upgrade" 0.209
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:326 7.567
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.377
Before features/support/hooks.rb:269 0.005
Given a computer 0.205
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.761
Then all tps features from the old Tails version are active 1.707
And Tails is running from USB drive "to_upgrade" 0.369
And the boot device has safe access rights 3.891
And the expected persistent files created with the old Tails version are present in the filesystem 1.675
And all persistent directories from the old Tails version have safe access rights 2.767
After features/support/hooks.rb:326 0.711
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:52.214
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 12.397
And no SquashFS delta is installed 0.470
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.313
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.432
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.515
When the network is plugged 0.084
And Tor is ready 24.052
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.752
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.104
Given I shutdown Tails and wait for the computer to power off 10.990
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:17.264
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.768
And the file system changes introduced in version 6.2~testoverlayfs are present 0.302
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.354
# 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.316
When the network is plugged 0.072
And Tor is ready 20.478
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.428
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.640
Given I shutdown Tails and wait for the computer to power off 4.378
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.893
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.091
And the file system changes introduced in version 6.3~testoverlayfs are present 0.480
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.306
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.293
When the network is plugged 0.065
And Tor is ready 16.734
Then the Upgrader considers the system as up-to-date 0.317
# 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.516
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.138
After features/support/hooks.rb:326 1.030
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
51.094
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 24.634
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.412
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the signing key used by the Upgrader is outdated 1.153
But a current signing key is available on our website 0.000
When the network is plugged 0.080
And Tor is ready 17.747
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.997
After features/support/hooks.rb:326 1.764
After features/support/hooks.rb:100 0.000