Project Number Date
test_Tails_ISO_20530-tca-controls-tor-flag-file 41 08 Dec 2024, 21:00

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:41.645 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:16.090
Before features/support/hooks.rb:269 0.004
Given a computer 0.187
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 29.420
When I start Tails from USB drive "old" with network unplugged 1:40.962
Then the boot device has safe access rights 3.250
And Tails is running from USB drive "old" 0.425
And there is no persistence partition on USB drive "old" 0.087
And process "udev-watchdog" is running 0.115
And udev-watchdog is monitoring the correct device 0.344
And I unplug USB drive "old" 0.200
After features/support/hooks.rb:326 3.506
After features/support/hooks.rb:100 0.038
Tags: @product
2:16.968
Before features/support/hooks.rb:269 0.007
Given a computer 0.208
And I start Tails from USB drive "old" with network unplugged and I login 1:31.179
Then Tails is running from USB drive "old" 0.368
And I create a persistent partition 33.288
And I take note of which tps features are available 2.588
Then a Tails persistence partition exists on USB drive "old" 0.842
And I shutdown Tails and wait for the computer to power off 8.493
After features/support/hooks.rb:326 0.171
After features/support/hooks.rb:100 0.010
Tags: @product
2:52.111
Before features/support/hooks.rb:269 0.007
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.895
Then Tails is running from USB drive "old" 1.222
And all tps features are active 2.109
When I write some files expected to persist 1.713
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.244
And all persistence configuration files have safe access rights 0.416
And all persistent directories from the old Tails version have safe access rights 2.578
And I take note of which tps features are available 0.456
And I shutdown Tails and wait for the computer to power off 4.442
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.828
After features/support/hooks.rb:326 0.231
After features/support/hooks.rb:100 0.012
Tags: @product
2:32.978
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 10.910
And I log in to a new session 17.801
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.516
And I plug USB drive "to_upgrade" 2.517
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.074
Then the running Tails is installed on USB drive "to_upgrade" 18.505
And I unplug USB drive "to_upgrade" 0.211
And I unplug USB drive "__internal" 0.441
After features/support/hooks.rb:326 2.611
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.719
Before features/support/hooks.rb:269 0.006
Given a computer 0.205
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.865
Then all tps features from the old Tails version are active 1.615
And Tails is running from USB drive "to_upgrade" 0.371
And the boot device has safe access rights 3.543
And the expected persistent files created with the old Tails version are present in the filesystem 1.499
And all persistent directories from the old Tails version have safe access rights 2.617
After features/support/hooks.rb:326 1.484
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
6:47.046
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.652
And no SquashFS delta is installed 0.108
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.451
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
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.470
When the network is plugged 0.071
And Tor is ready 19.714
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.322
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.027
Given I shutdown Tails and wait for the computer to power off 11.385
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.990
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.440
And the file system changes introduced in version 6.2~testoverlayfs are present 0.335
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.318
# 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.286
When the network is plugged 0.082
And Tor is ready 15.739
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.958
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.079
Given I shutdown Tails and wait for the computer to power off 4.350
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.483
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 4.722
And the file system changes introduced in version 6.3~testoverlayfs are present 0.524
And only the 6.3~testoverlayfs SquashFS delta is installed 0.087
# 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.416
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.338
When the network is plugged 0.479
And Tor is ready 18.057
Then the Upgrader considers the system as up-to-date 0.363
# 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.129
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.151
After features/support/hooks.rb:326 0.802
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
35.731
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 11.816
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.353
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.077
And the signing key used by the Upgrader is outdated 0.910
But a current signing key is available on our website 0.000
When the network is plugged 0.086
And Tor is ready 15.904
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.581
After features/support/hooks.rb:326 0.918
After features/support/hooks.rb:100 0.000