Project Number Date
test_Tails_ISO_20530-tca-controls-tor-flag-file 29 25 Nov 2024, 21:48

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 18:36.199 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:0.593
Before features/support/hooks.rb:269 0.007
Given a computer 0.195
And I create a 7200 MiB disk named "old" 0.039
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 29.256
When I start Tails from USB drive "old" with network unplugged 1:26.006
Then the boot device has safe access rights 2.918
And Tails is running from USB drive "old" 0.328
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.395
And I unplug USB drive "old" 0.225
After features/support/hooks.rb:326 3.523
After features/support/hooks.rb:100 0.010
Tags: @product
2:5.647
Before features/support/hooks.rb:269 0.006
Given a computer 0.233
And I start Tails from USB drive "old" with network unplugged and I login 1:22.151
Then Tails is running from USB drive "old" 0.351
And I create a persistent partition 32.487
And I take note of which tps features are available 1.427
Then a Tails persistence partition exists on USB drive "old" 0.825
And I shutdown Tails and wait for the computer to power off 8.171
After features/support/hooks.rb:326 0.230
After features/support/hooks.rb:100 0.011
Tags: @product
2:52.068
Before features/support/hooks.rb:269 0.006
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.161
Then Tails is running from USB drive "old" 0.387
And all tps features are active 1.964
When I write some files expected to persist 1.753
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.312
And all persistence configuration files have safe access rights 0.571
And all persistent directories from the old Tails version have safe access rights 2.422
And I take note of which tps features are available 0.450
And I shutdown Tails and wait for the computer to power off 4.328
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.523
After features/support/hooks.rb:326 0.121
After features/support/hooks.rb:100 0.010
Tags: @product
2:27.195
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.992
And I log in to a new session 17.772
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.966
And I plug USB drive "to_upgrade" 2.422
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.928
Then the running Tails is installed on USB drive "to_upgrade" 19.657
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.249
After features/support/hooks.rb:326 1.993
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.000
Before features/support/hooks.rb:269 0.005
Given a computer 0.188
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.270
Then all tps features from the old Tails version are active 1.717
And Tails is running from USB drive "to_upgrade" 0.367
And the boot device has safe access rights 3.522
And the expected persistent files created with the old Tails version are present in the filesystem 1.482
And all persistent directories from the old Tails version have safe access rights 2.451
After features/support/hooks.rb:326 0.564
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:23.397
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 12.936
And no SquashFS delta is installed 0.125
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.353
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.248
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.456
When the network is plugged 0.065
And Tor is ready 18.190
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.525
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.391
Given I shutdown Tails and wait for the computer to power off 10.805
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.154
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.099
And the file system changes introduced in version 6.2~testoverlayfs are present 0.345
And only the 6.2~testoverlayfs SquashFS delta is installed 0.090
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.338
# 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.299
When the network is plugged 0.074
And Tor is ready 18.273
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.463
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.529
Given I shutdown Tails and wait for the computer to power off 4.281
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.949
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.890
And the file system changes introduced in version 6.3~testoverlayfs are present 0.473
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.344
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.287
When the network is plugged 0.072
And Tor is ready 16.121
Then the Upgrader considers the system as up-to-date 0.323
# 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.638
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.082
After features/support/hooks.rb:326 0.753
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
35.296
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 9.691
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.360
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.721
But a current signing key is available on our website 0.000
When the network is plugged 0.089
And Tor is ready 17.653
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.723
After features/support/hooks.rb:326 0.583
After features/support/hooks.rb:100 0.000