Project Number Date
test_Tails_ISO_20530-tca-controls-tor-flag-file 30 26 Nov 2024, 22:55

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:40.182 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:10.665
Before features/support/hooks.rb:269 0.004
Given a computer 0.203
And I create a 7200 MiB disk named "old" 0.065
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 34.044
When I start Tails from USB drive "old" with network unplugged 1:31.037
Then the boot device has safe access rights 3.120
And Tails is running from USB drive "old" 0.371
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.126
And udev-watchdog is monitoring the correct device 0.383
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:326 7.210
After features/support/hooks.rb:100 0.009
Tags: @product
2:15.399
Before features/support/hooks.rb:269 0.007
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login 1:28.304
Then Tails is running from USB drive "old" 0.332
And I create a persistent partition 35.029
And I take note of which tps features are available 1.718
Then a Tails persistence partition exists on USB drive "old" 0.902
And I shutdown Tails and wait for the computer to power off 8.902
After features/support/hooks.rb:326 0.170
After features/support/hooks.rb:100 0.007
Tags: @product
3:0.658
Before features/support/hooks.rb:269 0.004
Given a computer 0.208
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.168
Then Tails is running from USB drive "old" 0.387
And all tps features are active 2.158
When I write some files expected to persist 1.966
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.265
And all persistence configuration files have safe access rights 0.436
And all persistent directories from the old Tails version have safe access rights 2.558
And I take note of which tps features are available 0.453
And I shutdown Tails and wait for the computer to power off 4.413
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.641
After features/support/hooks.rb:326 0.201
After features/support/hooks.rb:100 0.009
Tags: @product
2:40.327
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 12.146
And I log in to a new session 23.195
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.465
And I plug USB drive "to_upgrade" 2.630
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.175
Then the running Tails is installed on USB drive "to_upgrade" 23.273
And I unplug USB drive "to_upgrade" 0.229
And I unplug USB drive "__internal" 0.210
After features/support/hooks.rb:326 3.792
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.546
Before features/support/hooks.rb:269 0.006
Given a computer 0.321
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.943
Then all tps features from the old Tails version are active 1.839
And Tails is running from USB drive "to_upgrade" 0.457
And the boot device has safe access rights 3.735
And the expected persistent files created with the old Tails version are present in the filesystem 1.539
And all persistent directories from the old Tails version have safe access rights 2.708
After features/support/hooks.rb:326 0.632
After features/support/hooks.rb:100 0.010
7:3.603
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.708
And no SquashFS delta is installed 0.098
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.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.535
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.492
When the network is plugged 0.066
And Tor is ready 48.424
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.607
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.419
Given I shutdown Tails and wait for the computer to power off 11.076
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.700
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.525
And the file system changes introduced in version 6.2~testoverlayfs are present 0.350
And only the 6.2~testoverlayfs SquashFS delta is installed 0.164
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.458
# 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.520
When the network is plugged 0.074
And Tor is ready 19.784
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.514
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.188
Given I shutdown Tails and wait for the computer to power off 4.682
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.228
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.355
And the file system changes introduced in version 6.3~testoverlayfs are present 0.516
And only the 6.3~testoverlayfs SquashFS delta is installed 0.089
# 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.298
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.301
When the network is plugged 0.077
And Tor is ready 16.709
Then the Upgrader considers the system as up-to-date 0.336
# 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.729
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.072
After features/support/hooks.rb:326 0.959
After features/support/hooks.rb:100 0.016
1:7.980
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.499
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 2.145
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.665
And the signing key used by the Upgrader is outdated 1.213
But a current signing key is available on our website 0.000
When the network is plugged 0.083
And Tor is ready 48.726
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.647
After features/support/hooks.rb:326 0.638
After features/support/hooks.rb:100 0.000