Project Number Date
test_Tails_ISO_20530-tca-controls-tor-flag-file 52 13 Dec 2024, 23:51

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:50.595 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:18.163
Before features/support/hooks.rb:269 0.007
Given a computer 0.241
And I create a 7200 MiB disk named "old" 0.061
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 34.207
When I start Tails from USB drive "old" with network unplugged 1:38.161
Then the boot device has safe access rights 3.292
And Tails is running from USB drive "old" 0.371
And there is no persistence partition on USB drive "old" 0.082
And process "udev-watchdog" is running 0.106
And udev-watchdog is monitoring the correct device 0.362
And I unplug USB drive "old" 0.217
After features/support/hooks.rb:326 3.792
After features/support/hooks.rb:100 0.010
Tags: @product
2:21.251
Before features/support/hooks.rb:269 0.006
Given a computer 0.226
And I start Tails from USB drive "old" with network unplugged and I login 1:34.861
Then Tails is running from USB drive "old" 0.402
And I create a persistent partition 34.165
And I take note of which tps features are available 1.520
Then a Tails persistence partition exists on USB drive "old" 0.923
And I shutdown Tails and wait for the computer to power off 9.151
After features/support/hooks.rb:326 0.201
After features/support/hooks.rb:100 0.011
Tags: @product
3:9.907
Before features/support/hooks.rb:269 0.004
Given a computer 0.297
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:26.936
Then Tails is running from USB drive "old" 1.330
And all tps features are active 2.433
When I write some files expected to persist 3.284
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.212
And all persistence configuration files have safe access rights 1.327
And all persistent directories from the old Tails version have safe access rights 2.559
And I take note of which tps features are available 0.518
And I shutdown Tails and wait for the computer to power off 4.585
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.420
After features/support/hooks.rb:326 0.259
After features/support/hooks.rb:100 0.009
Tags: @product
2:40.148
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.577
And I log in to a new session 21.817
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.883
And I plug USB drive "to_upgrade" 2.513
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.925
Then the running Tails is installed on USB drive "to_upgrade" 24.891
And I unplug USB drive "to_upgrade" 0.290
And I unplug USB drive "__internal" 0.249
After features/support/hooks.rb:326 2.515
After features/support/hooks.rb:100 0.000
Tags: @product
2:27.831
Before features/support/hooks.rb:269 0.005
Given a computer 0.433
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:16.247
Then all tps features from the old Tails version are active 2.680
And Tails is running from USB drive "to_upgrade" 0.342
And the boot device has safe access rights 3.692
And the expected persistent files created with the old Tails version are present in the filesystem 1.627
And all persistent directories from the old Tails version have safe access rights 2.807
After features/support/hooks.rb:326 0.947
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
7:15.290
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 16.416
And no SquashFS delta is installed 0.365
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.335
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.366
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.479
When the network is plugged 0.103
And Tor is ready 22.940
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.597
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.610
Given I shutdown Tails and wait for the computer to power off 11.291
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:19.919
Then Tails is running version 6.2~testoverlayfs 0.024
And all tps features are active 2.821
And the file system changes introduced in version 6.2~testoverlayfs are present 0.397
And only the 6.2~testoverlayfs SquashFS delta is installed 0.128
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.667
# 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.440
When the network is plugged 0.078
And Tor is ready 17.991
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.145
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.895
Given I shutdown Tails and wait for the computer to power off 4.528
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.390
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.436
And the file system changes introduced in version 6.3~testoverlayfs are present 0.591
And only the 6.3~testoverlayfs SquashFS delta is installed 0.061
# 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.421
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.431
When the network is plugged 0.069
And Tor is ready 14.770
Then the Upgrader considers the system as up-to-date 10.819
# 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.539
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.120
After features/support/hooks.rb:326 0.856
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
38.002
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 10.901
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.445
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.483
But a current signing key is available on our website 0.000
When the network is plugged 0.076
And Tor is ready 19.333
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.698
After features/support/hooks.rb:326 0.874
After features/support/hooks.rb:100 0.000