Project Number Date
test_Tails_ISO_20530-tca-controls-tor-flag-file 64 24 Dec 2024, 01:20

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:51.043 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:21.159
Before features/support/hooks.rb:269 0.004
Given a computer 0.317
And I create a 7200 MiB disk named "old" 0.062
And I plug USB drive "old" 1.062
And I write an old version of the Tails USB image to disk "old" 30.873
When I start Tails from USB drive "old" with network unplugged 1:44.521
Then the boot device has safe access rights 3.199
And Tails is running from USB drive "old" 0.388
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.108
And udev-watchdog is monitoring the correct device 0.344
And I unplug USB drive "old" 0.203
After features/support/hooks.rb:326 3.720
After features/support/hooks.rb:100 0.008
Tags: @product
2:23.370
Before features/support/hooks.rb:269 0.006
Given a computer 0.212
And I start Tails from USB drive "old" with network unplugged and I login 1:36.086
Then Tails is running from USB drive "old" 0.327
And I create a persistent partition 33.824
And I take note of which tps features are available 1.405
Then a Tails persistence partition exists on USB drive "old" 0.823
And I shutdown Tails and wait for the computer to power off 10.690
After features/support/hooks.rb:326 0.191
After features/support/hooks.rb:100 0.008
Tags: @product
3:14.139
Before features/support/hooks.rb:269 0.005
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:29.182
Then Tails is running from USB drive "old" 1.517
And all tps features are active 3.571
When I write some files expected to persist 3.288
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.263
And all persistence configuration files have safe access rights 0.439
And all persistent directories from the old Tails version have safe access rights 3.488
And I take note of which tps features are available 2.354
And I shutdown Tails and wait for the computer to power off 4.804
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.026
After features/support/hooks.rb:326 0.141
After features/support/hooks.rb:100 0.008
Tags: @product
2:37.530
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.701
And I log in to a new session 20.064
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.565
And I plug USB drive "to_upgrade" 2.438
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.656
Then the running Tails is installed on USB drive "to_upgrade" 23.613
And I unplug USB drive "to_upgrade" 0.252
And I unplug USB drive "__internal" 0.237
After features/support/hooks.rb:326 7.599
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.863
Before features/support/hooks.rb:269 0.006
Given a computer 0.226
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.769
Then all tps features from the old Tails version are active 1.898
And Tails is running from USB drive "to_upgrade" 0.424
And the boot device has safe access rights 4.001
And the expected persistent files created with the old Tails version are present in the filesystem 1.723
And all persistent directories from the old Tails version have safe access rights 2.819
After features/support/hooks.rb:326 0.716
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:10.977
Before features/support/hooks.rb:269 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.154
And no SquashFS delta is installed 0.088
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.415
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.096
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.343
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.479
When the network is plugged 0.127
And Tor is ready 20.949
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.343
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.683
Given I shutdown Tails and wait for the computer to power off 8.999
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.137
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.550
And the file system changes introduced in version 6.2~testoverlayfs are present 0.340
And only the 6.2~testoverlayfs SquashFS delta is installed 0.095
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.445
# 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.421
When the network is plugged 0.115
And Tor is ready 44.912
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.642
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.137
Given I shutdown Tails and wait for the computer to power off 4.285
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.043
Then Tails is running version 6.3~testoverlayfs 0.023
And all tps features are active 2.133
And the file system changes introduced in version 6.3~testoverlayfs are present 0.468
And only the 6.3~testoverlayfs SquashFS delta is installed 0.090
# 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.316
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.334
When the network is plugged 0.075
And Tor is ready 18.970
Then the Upgrader considers the system as up-to-date 0.327
# 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.373
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.033
After features/support/hooks.rb:326 0.833
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
39.003
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 11.683
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.301
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.082
But a current signing key is available on our website 0.000
When the network is plugged 0.083
And Tor is ready 20.003
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.789
After features/support/hooks.rb:326 1.451
After features/support/hooks.rb:100 0.000