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

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:0.805 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.522
Before features/support/hooks.rb:269 0.007
Given a computer 0.376
And I create a 7200 MiB disk named "old" 0.155
And I plug USB drive "old" 1.062
And I write an old version of the Tails USB image to disk "old" 30.673
When I start Tails from USB drive "old" with network unplugged 1:42.204
Then the boot device has safe access rights 3.085
And Tails is running from USB drive "old" 0.309
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.299
And I unplug USB drive "old" 0.195
After features/support/hooks.rb:326 7.085
After features/support/hooks.rb:100 0.010
Tags: @product
2:19.087
Before features/support/hooks.rb:269 0.005
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login 1:25.999
Then Tails is running from USB drive "old" 0.310
And I create a persistent partition 41.185
And I take note of which tps features are available 2.016
Then a Tails persistence partition exists on USB drive "old" 0.781
And I shutdown Tails and wait for the computer to power off 8.599
After features/support/hooks.rb:326 0.188
After features/support/hooks.rb:100 0.011
Tags: @product
3:2.565
Before features/support/hooks.rb:269 0.007
Given a computer 0.211
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:25.603
Then Tails is running from USB drive "old" 0.666
And all tps features are active 1.995
When I write some files expected to persist 1.729
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.215
And all persistence configuration files have safe access rights 0.418
And all persistent directories from the old Tails version have safe access rights 2.420
And I take note of which tps features are available 0.408
And I shutdown Tails and wait for the computer to power off 4.059
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.839
After features/support/hooks.rb:326 0.095
After features/support/hooks.rb:100 0.011
Tags: @product
2:33.570
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.575
And I log in to a new session 19.418
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.138
And I plug USB drive "to_upgrade" 2.436
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.158
Then the running Tails is installed on USB drive "to_upgrade" 23.451
And I unplug USB drive "to_upgrade" 0.190
And I unplug USB drive "__internal" 0.199
After features/support/hooks.rb:326 2.457
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.940
Before features/support/hooks.rb:269 0.006
Given a computer 0.196
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.091
Then all tps features from the old Tails version are active 1.658
And Tails is running from USB drive "to_upgrade" 0.347
And the boot device has safe access rights 3.603
And the expected persistent files created with the old Tails version are present in the filesystem 1.471
And all persistent directories from the old Tails version have safe access rights 2.572
After features/support/hooks.rb:326 0.660
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:50.022
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.614
And no SquashFS delta is installed 0.080
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.301
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
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.496
When the network is plugged 0.070
And Tor is ready 19.404
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.972
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.663
Given I shutdown Tails and wait for the computer to power off 8.662
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.334
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.343
And the file system changes introduced in version 6.2~testoverlayfs are present 0.317
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.300
# 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.394
When the network is plugged 0.088
And Tor is ready 19.185
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.843
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.987
Given I shutdown Tails and wait for the computer to power off 4.385
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.676
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.066
And the file system changes introduced in version 6.3~testoverlayfs are present 0.487
And only the 6.3~testoverlayfs SquashFS delta is installed 0.089
# 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.310
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.285
When the network is plugged 0.070
And Tor is ready 19.161
Then the Upgrader considers the system as up-to-date 10.769
# 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.197
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.972
After features/support/hooks.rb:326 0.763
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
39.096
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.716
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.404
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the signing key used by the Upgrader is outdated 0.835
But a current signing key is available on our website 0.000
When the network is plugged 0.076
And Tor is ready 19.091
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.916
After features/support/hooks.rb:326 0.632
After features/support/hooks.rb:100 0.000