Project Number Date
test_Tails_ISO_20530-tca-controls-tor-flag-file 83 21 Jan 2025, 23:09

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:20.820 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:15.168
Before features/support/hooks.rb:269 0.005
Given a computer 0.206
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 32.342
When I start Tails from USB drive "old" with network unplugged 1:37.310
Then the boot device has safe access rights 3.156
And Tails is running from USB drive "old" 0.366
And there is no persistence partition on USB drive "old" 0.081
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.319
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:326 3.899
After features/support/hooks.rb:100 0.010
Tags: @product
2:9.612
Before features/support/hooks.rb:269 0.006
Given a computer 0.197
And I start Tails from USB drive "old" with network unplugged and I login 1:23.939
Then Tails is running from USB drive "old" 0.395
And I create a persistent partition 34.373
And I take note of which tps features are available 1.313
Then a Tails persistence partition exists on USB drive "old" 0.829
And I shutdown Tails and wait for the computer to power off 8.565
After features/support/hooks.rb:326 0.169
After features/support/hooks.rb:100 0.010
Tags: @product
2:59.156
Before features/support/hooks.rb:269 0.005
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.977
Then Tails is running from USB drive "old" 1.189
And all tps features are active 3.562
When I write some files expected to persist 3.205
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.231
And all persistence configuration files have safe access rights 0.750
And all persistent directories from the old Tails version have safe access rights 2.633
And I take note of which tps features are available 1.024
And I shutdown Tails and wait for the computer to power off 4.232
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.165
After features/support/hooks.rb:326 0.129
After features/support/hooks.rb:100 0.010
Tags: @product
2:31.221
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 10.836
And I log in to a new session 18.354
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.569
And I plug USB drive "to_upgrade" 2.401
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.129
Then the running Tails is installed on USB drive "to_upgrade" 22.504
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.222
After features/support/hooks.rb:326 2.300
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.710
Before features/support/hooks.rb:269 0.006
Given a computer 0.194
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.645
Then all tps features from the old Tails version are active 1.605
And Tails is running from USB drive "to_upgrade" 0.376
And the boot device has safe access rights 3.786
And the expected persistent files created with the old Tails version are present in the filesystem 1.526
And all persistent directories from the old Tails version have safe access rights 2.576
After features/support/hooks.rb:326 0.628
After features/support/hooks.rb:100 0.011
6:35.542
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 12.238
And no SquashFS delta is installed 0.122
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.587
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.386
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.428
When the network is plugged 0.067
And Tor is ready 20.465
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.294
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.705
Given I shutdown Tails and wait for the computer to power off 11.199
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.902
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.583
And the file system changes introduced in version 6.2~testoverlayfs are present 0.350
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.353
# 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.365
When the network is plugged 0.078
And Tor is ready 18.869
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.270
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.977
Given I shutdown Tails and wait for the computer to power off 4.365
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.000
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.422
And the file system changes introduced in version 6.3~testoverlayfs are present 0.475
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.280
When the network is plugged 0.064
And Tor is ready 18.296
Then the Upgrader considers the system as up-to-date 0.310
# 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.457
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.052
After features/support/hooks.rb:326 0.753
After features/support/hooks.rb:100 0.019
37.408
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 10.213
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.328
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.133
And the signing key used by the Upgrader is outdated 0.077
But a current signing key is available on our website 0.000
When the network is plugged 0.081
And Tor is ready 19.488
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.085
After features/support/hooks.rb:326 0.863
After features/support/hooks.rb:100 0.000