Project Number Date
test_Tails_ISO_20448-tor-browser-14-force-all-tests 50 22 Sep 2024, 07:17

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 21:27.896 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:14.706
Before features/support/hooks.rb:269 0.004
Given a computer 0.191
And I create a 7200 MiB disk named "old" 0.063
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 31.876
When I start Tails from USB drive "old" with network unplugged 1:37.302
Then the boot device has safe access rights 3.202
And Tails is running from USB drive "old" 0.348
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.106
And udev-watchdog is monitoring the correct device 0.283
And I unplug USB drive "old" 0.203
After features/support/hooks.rb:326 7.777
After features/support/hooks.rb:100 0.009
Tags: @product
2:19.492
Before features/support/hooks.rb:269 0.005
Given a computer 0.197
And I start Tails from USB drive "old" with network unplugged and I login 1:35.209
Then Tails is running from USB drive "old" 0.432
And I create a persistent partition 31.967
And I take note of which tps features are available 2.270
Then a Tails persistence partition exists on USB drive "old" 0.883
And I shutdown Tails and wait for the computer to power off 8.531
After features/support/hooks.rb:326 0.187
After features/support/hooks.rb:100 0.011
Tags: @product
3:3.386
Before features/support/hooks.rb:269 0.006
Given a computer 0.228
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:25.518
Then Tails is running from USB drive "old" 0.330
And all tps features are active 2.046
When I write some files expected to persist 1.776
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.220
And all persistence configuration files have safe access rights 0.374
And all persistent directories from the old Tails version have safe access rights 2.360
And I take note of which tps features are available 0.502
And I shutdown Tails and wait for the computer to power off 4.390
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.637
After features/support/hooks.rb:326 0.150
After features/support/hooks.rb:100 0.020
Tags: @product
2:42.634
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.797
And I log in to a new session 21.705
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.092
And I plug USB drive "to_upgrade" 2.573
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.696
Then the running Tails is installed on USB drive "to_upgrade" 23.279
And I unplug USB drive "to_upgrade" 0.262
And I unplug USB drive "__internal" 0.226
After features/support/hooks.rb:326 6.771
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.882
Before features/support/hooks.rb:269 0.006
Given a computer 0.200
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.549
Then all tps features from the old Tails version are active 1.926
And Tails is running from USB drive "to_upgrade" 0.425
And the boot device has safe access rights 4.106
And the expected persistent files created with the old Tails version are present in the filesystem 1.625
And all persistent directories from the old Tails version have safe access rights 3.049
After features/support/hooks.rb:326 0.965
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
8:5.321
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 13.351
And no SquashFS delta is installed 0.126
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.433
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.477
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.484
When the network is plugged 0.079
And Tor is ready 23.923
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.999
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.083
Given I shutdown Tails and wait for the computer to power off 1:25.133
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:18.042
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.329
And the file system changes introduced in version 6.2~testoverlayfs are present 0.289
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.301
# 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.292
When the network is plugged 0.100
And Tor is ready 15.774
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.617
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.402
Given I shutdown Tails and wait for the computer to power off 4.420
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.883
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.284
And the file system changes introduced in version 6.3~testoverlayfs are present 0.599
And only the 6.3~testoverlayfs SquashFS delta is installed 0.087
# 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.343
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.333
When the network is plugged 0.081
And Tor is ready 21.246
Then the Upgrader considers the system as up-to-date 0.386
# 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.197
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.034
After features/support/hooks.rb:326 0.794
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
37.473
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.964
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.664
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.837
But a current signing key is available on our website 0.000
When the network is plugged 0.070
And Tor is ready 18.212
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.668
After features/support/hooks.rb:326 1.378
After features/support/hooks.rb:100 0.000