Project Number Date
test_Tails_ISO_20530-tca-controls-tor-flag-file 86 24 Jan 2025, 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:48.757 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:25.276
Before features/support/hooks.rb:269 0.006
Given a computer 0.183
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.083
And I write an old version of the Tails USB image to disk "old" 29.904
When I start Tails from USB drive "old" with network unplugged 1:49.320
Then the boot device has safe access rights 3.538
And Tails is running from USB drive "old" 0.370
And there is no persistence partition on USB drive "old" 0.094
And process "udev-watchdog" is running 0.127
And udev-watchdog is monitoring the correct device 0.372
And I unplug USB drive "old" 0.234
After features/support/hooks.rb:326 3.612
After features/support/hooks.rb:100 0.066
Tags: @product
2:23.192
Before features/support/hooks.rb:269 0.005
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login 1:37.641
Then Tails is running from USB drive "old" 0.345
And I create a persistent partition 33.192
And I take note of which tps features are available 1.533
Then a Tails persistence partition exists on USB drive "old" 0.881
And I shutdown Tails and wait for the computer to power off 9.397
After features/support/hooks.rb:326 0.978
After features/support/hooks.rb:100 0.022
Tags: @product
3:16.855
Before features/support/hooks.rb:269 0.009
Given a computer 0.699
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:35.895
Then Tails is running from USB drive "old" 1.187
And all tps features are active 2.056
When I write some files expected to persist 1.893
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.342
And all persistence configuration files have safe access rights 0.590
And all persistent directories from the old Tails version have safe access rights 4.117
And I take note of which tps features are available 0.533
And I shutdown Tails and wait for the computer to power off 4.325
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.213
After features/support/hooks.rb:326 0.110
After features/support/hooks.rb:100 0.009
Tags: @product
2:35.205
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.916
And I log in to a new session 20.043
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.766
And I plug USB drive "to_upgrade" 2.407
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.718
Then the running Tails is installed on USB drive "to_upgrade" 22.931
And I unplug USB drive "to_upgrade" 0.219
And I unplug USB drive "__internal" 0.202
After features/support/hooks.rb:326 2.209
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.736
Before features/support/hooks.rb:269 0.004
Given a computer 0.187
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.026
Then all tps features from the old Tails version are active 1.664
And Tails is running from USB drive "to_upgrade" 0.386
And the boot device has safe access rights 3.192
And the expected persistent files created with the old Tails version are present in the filesystem 1.679
And all persistent directories from the old Tails version have safe access rights 2.599
After features/support/hooks.rb:326 0.630
After features/support/hooks.rb:100 0.009
6:18.616
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 11.635
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.319
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.328
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.569
When the network is plugged 0.074
And Tor is ready 20.489
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.458
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.858
Given I shutdown Tails and wait for the computer to power off 8.225
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.959
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.183
And the file system changes introduced in version 6.2~testoverlayfs are present 0.321
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.439
# 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.288
When the network is plugged 0.061
And Tor is ready 17.686
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.486
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.900
Given I shutdown Tails and wait for the computer to power off 4.391
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.590
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.998
And the file system changes introduced in version 6.3~testoverlayfs are present 0.465
And only the 6.3~testoverlayfs SquashFS delta is installed 0.084
# 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.323
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.277
When the network is plugged 0.070
And Tor is ready 14.768
Then the Upgrader considers the system as up-to-date 0.319
# 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.647
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.167
After features/support/hooks.rb:326 0.847
After features/support/hooks.rb:100 0.025
31.874
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.378
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.415
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
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.080
And Tor is ready 17.291
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.579
After features/support/hooks.rb:326 0.871
After features/support/hooks.rb:100 0.000