Project Number Date
test_Tails_ISO_20530-tca-controls-tor-flag-file 46 11 Dec 2024, 18:16

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 21:11.204 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:16.196
Before features/support/hooks.rb:269 0.015
Given a computer 0.225
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 31.123
When I start Tails from USB drive "old" with network unplugged 1:39.356
Then the boot device has safe access rights 3.220
And Tails is running from USB drive "old" 0.367
And there is no persistence partition on USB drive "old" 0.082
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.347
And I unplug USB drive "old" 0.280
After features/support/hooks.rb:326 3.756
After features/support/hooks.rb:100 0.011
Tags: @product
2:12.075
Before features/support/hooks.rb:269 0.005
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login 1:27.770
Then Tails is running from USB drive "old" 0.389
And I create a persistent partition 32.532
And I take note of which tps features are available 1.577
Then a Tails persistence partition exists on USB drive "old" 0.850
And I shutdown Tails and wait for the computer to power off 8.753
After features/support/hooks.rb:326 0.205
After features/support/hooks.rb:100 0.011
Tags: @product
3:14.783
Before features/support/hooks.rb:269 0.007
Given a computer 0.241
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:34.638
Then Tails is running from USB drive "old" 0.491
And all tps features are active 2.212
When I write some files expected to persist 1.884
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.296
And all persistence configuration files have safe access rights 0.451
And all persistent directories from the old Tails version have safe access rights 2.783
And I take note of which tps features are available 0.504
And I shutdown Tails and wait for the computer to power off 4.301
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.977
After features/support/hooks.rb:326 0.120
After features/support/hooks.rb:100 0.011
Tags: @product
2:41.136
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 12.816
And I log in to a new session 22.470
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.169
And I plug USB drive "to_upgrade" 2.532
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.773
Then the running Tails is installed on USB drive "to_upgrade" 22.820
And I unplug USB drive "to_upgrade" 0.284
And I unplug USB drive "__internal" 0.268
After features/support/hooks.rb:326 7.368
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.230
Before features/support/hooks.rb:269 0.007
Given a computer 0.425
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.700
Then all tps features from the old Tails version are active 2.300
And Tails is running from USB drive "to_upgrade" 0.393
And the boot device has safe access rights 3.868
And the expected persistent files created with the old Tails version are present in the filesystem 1.814
And all persistent directories from the old Tails version have safe access rights 2.728
After features/support/hooks.rb:326 0.792
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
7:24.742
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 16.093
And no SquashFS delta is installed 0.128
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.399
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.330
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.503
When the network is plugged 0.073
And Tor is ready 20.150
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.923
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.499
Given I shutdown Tails and wait for the computer to power off 10.903
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.390
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.324
And the file system changes introduced in version 6.2~testoverlayfs are present 0.321
And only the 6.2~testoverlayfs SquashFS delta is installed 0.085
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.301
# 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.285
When the network is plugged 0.064
And Tor is ready 15.349
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.724
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.657
Given I shutdown Tails and wait for the computer to power off 4.680
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.286
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.335
And the file system changes introduced in version 6.3~testoverlayfs are present 0.588
And only the 6.3~testoverlayfs SquashFS delta is installed 0.102
# 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.317
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.324
When the network is plugged 0.371
And Tor is ready 46.079
Then the Upgrader considers the system as up-to-date 0.322
# 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.655
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.059
After features/support/hooks.rb:326 0.706
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
58.039
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.957
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.364
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 0.934
But a current signing key is available on our website 0.000
When the network is plugged 0.066
And Tor is ready 46.010
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.639
After features/support/hooks.rb:326 0.615
After features/support/hooks.rb:100 0.000