Project Number Date
test_Tails_ISO_20530-tca-controls-tor-flag-file 40 07 Dec 2024, 20:59

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.178 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.211
Before features/support/hooks.rb:269 0.005
Given a computer 0.178
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 30.527
When I start Tails from USB drive "old" with network unplugged 1:29.403
Then the boot device has safe access rights 3.030
And Tails is running from USB drive "old" 0.326
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.087
And udev-watchdog is monitoring the correct device 0.288
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:326 3.514
After features/support/hooks.rb:100 0.012
Tags: @product
2:21.717
Before features/support/hooks.rb:269 0.006
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login 1:38.730
Then Tails is running from USB drive "old" 0.341
And I create a persistent partition 31.225
And I take note of which tps features are available 1.768
Then a Tails persistence partition exists on USB drive "old" 0.831
And I shutdown Tails and wait for the computer to power off 8.628
After features/support/hooks.rb:326 0.165
After features/support/hooks.rb:100 0.008
Tags: @product
3:4.132
Before features/support/hooks.rb:269 0.005
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:25.860
Then Tails is running from USB drive "old" 0.502
And all tps features are active 1.988
When I write some files expected to persist 1.787
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.297
And all persistence configuration files have safe access rights 0.418
And all persistent directories from the old Tails version have safe access rights 2.790
And I take note of which tps features are available 0.474
And I shutdown Tails and wait for the computer to power off 4.489
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.324
After features/support/hooks.rb:326 0.158
After features/support/hooks.rb:100 0.010
Tags: @product
2:29.613
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 11.784
And I log in to a new session 19.708
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.950
And I plug USB drive "to_upgrade" 2.409
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.659
Then the running Tails is installed on USB drive "to_upgrade" 17.659
And I unplug USB drive "to_upgrade" 0.208
And I unplug USB drive "__internal" 0.232
After features/support/hooks.rb:326 3.972
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.769
Before features/support/hooks.rb:269 0.008
Given a computer 0.204
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.462
Then all tps features from the old Tails version are active 1.855
And Tails is running from USB drive "to_upgrade" 0.373
And the boot device has safe access rights 3.563
And the expected persistent files created with the old Tails version are present in the filesystem 1.531
And all persistent directories from the old Tails version have safe access rights 2.777
After features/support/hooks.rb:326 0.646
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
6:39.165
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.132
And no SquashFS delta is installed 0.081
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.337
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.312
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.610
When the network is plugged 0.079
And Tor is ready 18.734
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.932
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.792
Given I shutdown Tails and wait for the computer to power off 11.008
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.634
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.368
And the file system changes introduced in version 6.2~testoverlayfs are present 0.334
And only the 6.2~testoverlayfs SquashFS delta is installed 0.084
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.393
# 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.429
When the network is plugged 0.079
And Tor is ready 16.901
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.740
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.383
Given I shutdown Tails and wait for the computer to power off 4.415
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.449
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.053
And the file system changes introduced in version 6.3~testoverlayfs are present 0.493
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.322
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.438
When the network is plugged 0.089
And Tor is ready 19.705
Then the Upgrader considers the system as up-to-date 0.354
# 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.101
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.218
After features/support/hooks.rb:326 0.663
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
36.568
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 10.921
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.413
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.828
But a current signing key is available on our website 0.000
When the network is plugged 0.095
And Tor is ready 17.258
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.989
After features/support/hooks.rb:326 0.919
After features/support/hooks.rb:100 0.000