Project Number Date
test_Tails_ISO_20530-tca-controls-tor-flag-file 25 21 Nov 2024, 22:57

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:13.573 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:23.986
Before features/support/hooks.rb:269 0.005
Given a computer 0.225
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.068
And I write an old version of the Tails USB image to disk "old" 32.810
When I start Tails from USB drive "old" with network unplugged 1:45.757
Then the boot device has safe access rights 3.061
And Tails is running from USB drive "old" 0.346
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.105
And udev-watchdog is monitoring the correct device 0.299
And I unplug USB drive "old" 0.192
After features/support/hooks.rb:326 3.578
After features/support/hooks.rb:100 0.044
Tags: @product
2:11.841
Before features/support/hooks.rb:269 0.004
Given a computer 0.205
And I start Tails from USB drive "old" with network unplugged and I login 1:26.028
Then Tails is running from USB drive "old" 0.405
And I create a persistent partition 34.182
And I take note of which tps features are available 1.561
Then a Tails persistence partition exists on USB drive "old" 0.863
And I shutdown Tails and wait for the computer to power off 8.594
After features/support/hooks.rb:326 0.208
After features/support/hooks.rb:100 0.009
Tags: @product
3:14.799
Before features/support/hooks.rb:269 0.005
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:33.336
Then Tails is running from USB drive "old" 1.414
And all tps features are active 2.096
When I write some files expected to persist 3.300
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.257
And all persistence configuration files have safe access rights 0.402
And all persistent directories from the old Tails version have safe access rights 3.351
And I take note of which tps features are available 0.543
And I shutdown Tails and wait for the computer to power off 4.406
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.500
After features/support/hooks.rb:326 0.159
After features/support/hooks.rb:100 0.007
Tags: @product
2:33.129
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 12.119
And I log in to a new session 22.150
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.717
And I plug USB drive "to_upgrade" 2.406
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.433
Then the running Tails is installed on USB drive "to_upgrade" 19.857
And I unplug USB drive "to_upgrade" 0.207
And I unplug USB drive "__internal" 0.237
After features/support/hooks.rb:326 3.574
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.112
Before features/support/hooks.rb:269 0.007
Given a computer 0.199
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.259
Then all tps features from the old Tails version are active 1.991
And Tails is running from USB drive "to_upgrade" 0.464
And the boot device has safe access rights 3.786
And the expected persistent files created with the old Tails version are present in the filesystem 1.467
And all persistent directories from the old Tails version have safe access rights 2.943
After features/support/hooks.rb:326 0.700
After features/support/hooks.rb:100 0.009
6:51.013
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.308
And no SquashFS delta is installed 0.124
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.352
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.328
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.455
When the network is plugged 0.102
And Tor is ready 21.408
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.226
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.824
Given I shutdown Tails and wait for the computer to power off 11.415
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:20.443
Then Tails is running version 6.2~testoverlayfs 0.029
And all tps features are active 2.813
And the file system changes introduced in version 6.2~testoverlayfs are present 0.339
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.315
# 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.332
When the network is plugged 0.067
And Tor is ready 16.205
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.176
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.780
Given I shutdown Tails and wait for the computer to power off 4.563
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.538
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.208
And the file system changes introduced in version 6.3~testoverlayfs are present 0.507
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.346
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.285
When the network is plugged 0.071
And Tor is ready 20.004
Then the Upgrader considers the system as up-to-date 0.323
# 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 13.921
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.933
After features/support/hooks.rb:326 0.716
After features/support/hooks.rb:100 0.018
37.691
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.965
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.320
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the signing key used by the Upgrader is outdated 2.029
But a current signing key is available on our website 0.000
When the network is plugged 0.106
And Tor is ready 17.574
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.621
After features/support/hooks.rb:326 0.661
After features/support/hooks.rb:100 0.000