Project Number Date
test_Tails_ISO_20530-tca-controls-tor-flag-file 43 10 Dec 2024, 20:56

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 21:7.797 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:31.502
Before features/support/hooks.rb:269 0.006
Given a computer 0.260
And I create a 7200 MiB disk named "old" 0.075
And I plug USB drive "old" 1.062
And I write an old version of the Tails USB image to disk "old" 31.479
When I start Tails from USB drive "old" with network unplugged 1:54.487
Then the boot device has safe access rights 3.177
And Tails is running from USB drive "old" 0.295
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.307
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:326 7.379
After features/support/hooks.rb:100 0.013
Tags: @product
2:11.030
Before features/support/hooks.rb:269 0.008
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login 1:29.365
Then Tails is running from USB drive "old" 0.405
And I create a persistent partition 32.127
And I take note of which tps features are available 1.706
Then a Tails persistence partition exists on USB drive "old" 0.783
And I shutdown Tails and wait for the computer to power off 6.450
After features/support/hooks.rb:326 0.179
After features/support/hooks.rb:100 0.014
Tags: @product
2:54.026
Before features/support/hooks.rb:269 0.007
Given a computer 0.201
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.275
Then Tails is running from USB drive "old" 0.609
And all tps features are active 2.002
When I write some files expected to persist 1.878
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.341
And all persistence configuration files have safe access rights 1.576
And all persistent directories from the old Tails version have safe access rights 2.468
And I take note of which tps features are available 0.428
And I shutdown Tails and wait for the computer to power off 4.501
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.741
After features/support/hooks.rb:326 0.107
After features/support/hooks.rb:100 0.011
Tags: @product
2:31.061
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 13.246
And I log in to a new session 19.688
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.996
And I plug USB drive "to_upgrade" 2.452
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.094
Then the running Tails is installed on USB drive "to_upgrade" 18.027
And I unplug USB drive "to_upgrade" 0.266
And I unplug USB drive "__internal" 0.289
After features/support/hooks.rb:326 3.735
After features/support/hooks.rb:100 0.000
Tags: @product
2:23.217
Before features/support/hooks.rb:269 0.007
Given a computer 0.180
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.569
Then all tps features from the old Tails version are active 1.648
And Tails is running from USB drive "to_upgrade" 0.378
And the boot device has safe access rights 3.377
And the expected persistent files created with the old Tails version are present in the filesystem 1.628
And all persistent directories from the old Tails version have safe access rights 2.435
After features/support/hooks.rb:326 0.773
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
8:1.794
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.223
And no SquashFS delta is installed 0.100
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.648
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.337
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.509
When the network is plugged 0.080
And Tor is ready 26.111
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.717
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.637
Given I shutdown Tails and wait for the computer to power off 1:22.419
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.414
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.201
And the file system changes introduced in version 6.2~testoverlayfs are present 0.306
And only the 6.2~testoverlayfs SquashFS delta is installed 0.076
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.342
# 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.266
When the network is plugged 0.072
And Tor is ready 18.308
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.028
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.063
Given I shutdown Tails and wait for the computer to power off 4.451
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.747
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.011
And the file system changes introduced in version 6.3~testoverlayfs are present 0.519
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.330
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.417
When the network is plugged 0.080
And Tor is ready 15.368
Then the Upgrader considers the system as up-to-date 10.928
# 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.731
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.172
After features/support/hooks.rb:326 0.779
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
35.164
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.976
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.670
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 1.093
But a current signing key is available on our website 0.000
When the network is plugged 0.069
And Tor is ready 15.406
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.888
After features/support/hooks.rb:326 0.736
After features/support/hooks.rb:100 0.000