Project Number Date
test_Tails_ISO_20530-tca-controls-tor-flag-file 42 09 Dec 2024, 20:47

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:16.839 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:10.700
Before features/support/hooks.rb:269 0.005
Given a computer 0.159
And I create a 7200 MiB disk named "old" 0.036
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 30.649
When I start Tails from USB drive "old" with network unplugged 1:34.754
Then the boot device has safe access rights 3.085
And Tails is running from USB drive "old" 0.297
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.295
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:326 3.515
After features/support/hooks.rb:100 0.009
Tags: @product
2:9.155
Before features/support/hooks.rb:269 0.006
Given a computer 0.176
And I start Tails from USB drive "old" with network unplugged and I login 1:26.260
Then Tails is running from USB drive "old" 0.344
And I create a persistent partition 32.000
And I take note of which tps features are available 1.280
Then a Tails persistence partition exists on USB drive "old" 0.804
And I shutdown Tails and wait for the computer to power off 8.287
After features/support/hooks.rb:326 0.173
After features/support/hooks.rb:100 0.009
Tags: @product
3:4.419
Before features/support/hooks.rb:269 0.005
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:25.007
Then Tails is running from USB drive "old" 1.684
And all tps features are active 1.940
When I write some files expected to persist 1.617
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.211
And all persistence configuration files have safe access rights 0.350
And all persistent directories from the old Tails version have safe access rights 2.338
And I take note of which tps features are available 0.456
And I shutdown Tails and wait for the computer to power off 6.220
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.410
After features/support/hooks.rb:326 0.120
After features/support/hooks.rb:100 0.007
Tags: @product
2:29.037
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 10.300
And I log in to a new session 18.210
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.171
And I plug USB drive "to_upgrade" 2.606
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.061
Then the running Tails is installed on USB drive "to_upgrade" 21.274
And I unplug USB drive "to_upgrade" 0.199
And I unplug USB drive "__internal" 0.213
After features/support/hooks.rb:326 2.007
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.090
Before features/support/hooks.rb:269 0.006
Given a computer 0.243
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.691
Then all tps features from the old Tails version are active 1.566
And Tails is running from USB drive "to_upgrade" 0.388
And the boot device has safe access rights 3.440
And the expected persistent files created with the old Tails version are present in the filesystem 1.362
And all persistent directories from the old Tails version have safe access rights 2.396
After features/support/hooks.rb:326 0.732
After features/support/hooks.rb:100 0.009
6:30.736
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 14.622
And no SquashFS delta is installed 0.120
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.285
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.327
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.517
When the network is plugged 0.062
And Tor is ready 20.018
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.408
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.341
Given I shutdown Tails and wait for the computer to power off 8.583
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.933
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.043
And the file system changes introduced in version 6.2~testoverlayfs are present 0.326
And only the 6.2~testoverlayfs SquashFS delta is installed 0.124
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.401
# 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.447
When the network is plugged 0.089
And Tor is ready 18.336
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.554
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.596
Given I shutdown Tails and wait for the computer to power off 4.373
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.636
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 5.209
And the file system changes introduced in version 6.3~testoverlayfs are present 0.637
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.460
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.278
When the network is plugged 0.075
And Tor is ready 19.118
Then the Upgrader considers the system as up-to-date 0.342
# 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.217
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.086
After features/support/hooks.rb:326 0.659
After features/support/hooks.rb:100 0.019
38.700
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.927
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.155
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.076
And the signing key used by the Upgrader is outdated 1.231
But a current signing key is available on our website 0.000
When the network is plugged 0.067
And Tor is ready 19.363
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.878
After features/support/hooks.rb:326 1.259
After features/support/hooks.rb:100 0.000