Project Number Date
test_Tails_ISO_20530-tca-controls-tor-flag-file 17 15 Nov 2024, 00:15

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:21.533 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:13.355
Before features/support/hooks.rb:269 0.003
Given a computer 0.173
And I create a 7200 MiB disk named "old" 0.068
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 30.992
When I start Tails from USB drive "old" with network unplugged 1:36.700
Then the boot device has safe access rights 3.222
And Tails is running from USB drive "old" 0.406
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.104
And udev-watchdog is monitoring the correct device 0.344
And I unplug USB drive "old" 0.214
After features/support/hooks.rb:326 3.548
After features/support/hooks.rb:100 0.010
Tags: @product
2:9.586
Before features/support/hooks.rb:269 0.006
Given a computer 0.226
And I start Tails from USB drive "old" with network unplugged and I login 1:25.955
Then Tails is running from USB drive "old" 0.340
And I create a persistent partition 31.868
And I take note of which tps features are available 1.741
Then a Tails persistence partition exists on USB drive "old" 0.923
And I shutdown Tails and wait for the computer to power off 8.529
After features/support/hooks.rb:326 0.171
After features/support/hooks.rb:100 0.008
Tags: @product
3:4.422
Before features/support/hooks.rb:269 0.005
Given a computer 0.218
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:26.723
Then Tails is running from USB drive "old" 0.438
And all tps features are active 1.993
When I write some files expected to persist 1.865
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.262
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.594
And I take note of which tps features are available 0.482
And I shutdown Tails and wait for the computer to power off 4.354
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.037
After features/support/hooks.rb:326 0.118
After features/support/hooks.rb:100 0.009
Tags: @product
2:31.832
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.199
And I log in to a new session 19.712
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.439
And I plug USB drive "to_upgrade" 2.415
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.871
Then the running Tails is installed on USB drive "to_upgrade" 21.767
And I unplug USB drive "to_upgrade" 0.209
And I unplug USB drive "__internal" 0.217
After features/support/hooks.rb:326 6.905
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.885
Before features/support/hooks.rb:269 0.006
Given a computer 0.210
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.754
Then all tps features from the old Tails version are active 1.898
And Tails is running from USB drive "to_upgrade" 0.357
And the boot device has safe access rights 3.349
And the expected persistent files created with the old Tails version are present in the filesystem 1.741
And all persistent directories from the old Tails version have safe access rights 2.574
After features/support/hooks.rb:326 0.975
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
6:32.169
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.390
And no SquashFS delta is installed 0.086
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.385
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.100
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.319
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.542
When the network is plugged 0.069
And Tor is ready 20.387
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.432
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.737
Given I shutdown Tails and wait for the computer to power off 8.918
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.593
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 3.441
And the file system changes introduced in version 6.2~testoverlayfs are present 0.309
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.330
# 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.288
When the network is plugged 0.073
And Tor is ready 17.928
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.831
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.029
Given I shutdown Tails and wait for the computer to power off 4.369
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.085
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.276
And the file system changes introduced in version 6.3~testoverlayfs are present 0.479
And only the 6.3~testoverlayfs SquashFS delta is installed 0.101
# 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.362
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.268
When the network is plugged 0.076
And Tor is ready 17.300
Then the Upgrader considers the system as up-to-date 0.312
# 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.249
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.980
After features/support/hooks.rb:326 0.800
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
35.281
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.295
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.485
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the signing key used by the Upgrader is outdated 0.799
But a current signing key is available on our website 0.000
When the network is plugged 0.085
And Tor is ready 16.384
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.161
After features/support/hooks.rb:326 1.406
After features/support/hooks.rb:100 0.000