Project Number Date
test_Tails_ISO_sysadmin-17987-torbrowser-archive 7 24 Oct 2024, 05:56

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:46.707 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
1:58.411
Before features/support/hooks.rb:269 0.004
Given a computer 0.172
And I create a 7200 MiB disk named "old" 0.054
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 29.274
When I start Tails from USB drive "old" with network unplugged 1:23.694
Then the boot device has safe access rights 3.127
And Tails is running from USB drive "old" 0.329
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.089
And udev-watchdog is monitoring the correct device 0.346
And I unplug USB drive "old" 0.202
After features/support/hooks.rb:326 3.550
After features/support/hooks.rb:100 0.009
Tags: @product
2:6.958
Before features/support/hooks.rb:269 0.005
Given a computer 0.193
And I start Tails from USB drive "old" with network unplugged and I login 1:23.229
Then Tails is running from USB drive "old" 0.326
And I create a persistent partition 32.627
And I take note of which tps features are available 1.604
Then a Tails persistence partition exists on USB drive "old" 0.830
And I shutdown Tails and wait for the computer to power off 8.147
After features/support/hooks.rb:326 0.196
After features/support/hooks.rb:100 0.010
Tags: @product
2:52.279
Before features/support/hooks.rb:269 0.004
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.176
Then Tails is running from USB drive "old" 0.806
And all tps features are active 1.897
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.246
And all persistence configuration files have safe access rights 1.393
And all persistent directories from the old Tails version have safe access rights 2.286
And I take note of which tps features are available 0.468
And I shutdown Tails and wait for the computer to power off 4.151
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.898
After features/support/hooks.rb:326 0.119
After features/support/hooks.rb:100 0.008
Tags: @product
2:26.063
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.418
And I log in to a new session 18.589
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.766
And I plug USB drive "to_upgrade" 2.438
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.121
Then the running Tails is installed on USB drive "to_upgrade" 19.328
And I unplug USB drive "to_upgrade" 0.191
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:326 5.031
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.035
Before features/support/hooks.rb:269 0.005
Given a computer 0.215
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.466
Then all tps features from the old Tails version are active 1.753
And Tails is running from USB drive "to_upgrade" 0.344
And the boot device has safe access rights 3.543
And the expected persistent files created with the old Tails version are present in the filesystem 1.363
And all persistent directories from the old Tails version have safe access rights 2.347
After features/support/hooks.rb:326 0.896
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:28.355
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.868
And no SquashFS delta is installed 0.128
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.401
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.136
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.296
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.444
When the network is plugged 0.063
And Tor is ready 18.008
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.352
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.126
Given I shutdown Tails and wait for the computer to power off 10.538
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.060
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.107
And the file system changes introduced in version 6.2~testoverlayfs are present 0.277
And only the 6.2~testoverlayfs SquashFS delta is installed 0.081
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.280
# 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.347
When the network is plugged 0.074
And Tor is ready 18.035
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.692
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.208
Given I shutdown Tails and wait for the computer to power off 6.740
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.903
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.427
And the file system changes introduced in version 6.3~testoverlayfs are present 0.537
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.336
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.305
When the network is plugged 0.149
And Tor is ready 18.626
Then the Upgrader considers the system as up-to-date 10.798
# 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 13.931
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.965
After features/support/hooks.rb:326 0.798
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
38.601
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 15.665
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.058
And the signing key used by the Upgrader is outdated 0.774
But a current signing key is available on our website 0.000
When the network is plugged 0.153
And Tor is ready 14.973
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.387
After features/support/hooks.rb:326 1.018
After features/support/hooks.rb:100 0.000