Project Number Date
test_Tails_ISO_20530-tca-controls-tor-flag-file 7 03 Nov 2024, 20:42

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:31.052 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:9.455
Before features/support/hooks.rb:269 0.004
Given a computer 0.177
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.064
And I write an old version of the Tails USB image to disk "old" 31.129
When I start Tails from USB drive "old" with network unplugged 1:32.830
Then the boot device has safe access rights 3.133
And Tails is running from USB drive "old" 0.372
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.105
And udev-watchdog is monitoring the correct device 0.321
And I unplug USB drive "old" 0.207
After features/support/hooks.rb:326 7.198
After features/support/hooks.rb:100 0.010
Tags: @product
2:16.874
Before features/support/hooks.rb:269 0.005
Given a computer 0.212
And I start Tails from USB drive "old" with network unplugged and I login 1:32.575
Then Tails is running from USB drive "old" 0.424
And I create a persistent partition 32.951
And I take note of which tps features are available 1.512
Then a Tails persistence partition exists on USB drive "old" 0.908
And I shutdown Tails and wait for the computer to power off 8.289
After features/support/hooks.rb:326 0.254
After features/support/hooks.rb:100 0.008
Tags: @product
2:59.651
Before features/support/hooks.rb:269 0.004
Given a computer 0.169
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.297
Then Tails is running from USB drive "old" 0.394
And all tps features are active 2.150
When I write some files expected to persist 1.742
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.221
And all persistence configuration files have safe access rights 0.339
And all persistent directories from the old Tails version have safe access rights 2.573
And I take note of which tps features are available 0.627
And I shutdown Tails and wait for the computer to power off 6.566
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.567
After features/support/hooks.rb:326 0.153
After features/support/hooks.rb:100 0.008
Tags: @product
2:37.124
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.736
And I log in to a new session 21.334
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.569
And I plug USB drive "to_upgrade" 2.383
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.119
Then the running Tails is installed on USB drive "to_upgrade" 18.564
And I unplug USB drive "to_upgrade" 0.212
And I unplug USB drive "__internal" 0.204
After features/support/hooks.rb:326 7.019
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.335
Before features/support/hooks.rb:269 0.005
Given a computer 0.183
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.825
Then all tps features from the old Tails version are active 1.949
And Tails is running from USB drive "to_upgrade" 0.305
And the boot device has safe access rights 3.257
And the expected persistent files created with the old Tails version are present in the filesystem 1.459
And all persistent directories from the old Tails version have safe access rights 2.354
After features/support/hooks.rb:326 0.639
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:41.283
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.995
And no SquashFS delta is installed 0.095
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.563
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.299
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.477
When the network is plugged 0.090
And Tor is ready 46.495
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.606
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.355
Given I shutdown Tails and wait for the computer to power off 8.520
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.928
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.345
And the file system changes introduced in version 6.2~testoverlayfs are present 0.302
And only the 6.2~testoverlayfs SquashFS delta is installed 0.083
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.423
# 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.325
When the network is plugged 0.072
And Tor is ready 18.861
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.946
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.785
Given I shutdown Tails and wait for the computer to power off 4.575
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.840
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.007
And the file system changes introduced in version 6.3~testoverlayfs are present 0.563
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.327
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.287
When the network is plugged 0.069
And Tor is ready 17.447
Then the Upgrader considers the system as up-to-date 0.325
# 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.072
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.032
After features/support/hooks.rb:326 0.732
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
34.327
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.836
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.274
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.847
But a current signing key is available on our website 0.000
When the network is plugged 0.063
And Tor is ready 16.671
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.581
After features/support/hooks.rb:326 0.666
After features/support/hooks.rb:100 0.000