Project Number Date
test_Tails_ISO_20530-tca-controls-tor-flag-file 33 29 Nov 2024, 20:39

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:9.857 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
1:57.655
Before features/support/hooks.rb:269 0.006
Given a computer 0.170
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 30.178
When I start Tails from USB drive "old" with network unplugged 1:22.221
Then the boot device has safe access rights 3.056
And Tails is running from USB drive "old" 0.285
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.089
And udev-watchdog is monitoring the correct device 0.304
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:326 3.547
After features/support/hooks.rb:100 0.009
Tags: @product
2:5.521
Before features/support/hooks.rb:269 0.006
Given a computer 0.167
And I start Tails from USB drive "old" with network unplugged and I login 1:22.983
Then Tails is running from USB drive "old" 0.341
And I create a persistent partition 31.642
And I take note of which tps features are available 1.332
Then a Tails persistence partition exists on USB drive "old" 0.750
And I shutdown Tails and wait for the computer to power off 8.302
After features/support/hooks.rb:326 0.188
After features/support/hooks.rb:100 0.009
Tags: @product
2:48.215
Before features/support/hooks.rb:269 0.006
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.814
Then Tails is running from USB drive "old" 0.350
And all tps features are active 1.835
When I write some files expected to persist 1.654
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.204
And all persistence configuration files have safe access rights 0.364
And all persistent directories from the old Tails version have safe access rights 2.236
And I take note of which tps features are available 0.373
And I shutdown Tails and wait for the computer to power off 4.270
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.926
After features/support/hooks.rb:326 0.114
After features/support/hooks.rb:100 0.010
Tags: @product
2:28.224
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.150
And I log in to a new session 18.770
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.932
And I plug USB drive "to_upgrade" 2.390
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.254
Then the running Tails is installed on USB drive "to_upgrade" 19.313
And I unplug USB drive "to_upgrade" 0.211
And I unplug USB drive "__internal" 0.200
After features/support/hooks.rb:326 2.464
After features/support/hooks.rb:100 0.000
Tags: @product
2:7.365
Before features/support/hooks.rb:269 0.006
Given a computer 0.175
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:58.264
Then all tps features from the old Tails version are active 1.579
And Tails is running from USB drive "to_upgrade" 0.304
And the boot device has safe access rights 3.065
And the expected persistent files created with the old Tails version are present in the filesystem 1.409
And all persistent directories from the old Tails version have safe access rights 2.566
After features/support/hooks.rb:326 0.604
After features/support/hooks.rb:100 0.009
6:45.424
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 11.277
And no SquashFS delta is installed 0.077
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.341
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.268
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.422
When the network is plugged 0.060
And Tor is ready 48.039
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.563
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.398
Given I shutdown Tails and wait for the computer to power off 8.421
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.544
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 1.915
And the file system changes introduced in version 6.2~testoverlayfs are present 0.298
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.287
# 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.243
When the network is plugged 0.056
And Tor is ready 17.346
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.232
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.471
Given I shutdown Tails and wait for the computer to power off 4.328
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.078
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.838
And the file system changes introduced in version 6.3~testoverlayfs are present 0.582
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.290
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.246
When the network is plugged 0.077
And Tor is ready 17.643
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 14.544
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.648
After features/support/hooks.rb:100 0.019
57.450
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 9.593
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.288
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the signing key used by the Upgrader is outdated 1.055
But a current signing key is available on our website 0.000
When the network is plugged 0.075
And Tor is ready 45.802
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.573
After features/support/hooks.rb:326 0.866
After features/support/hooks.rb:100 0.000