Project Number Date
test_Tails_ISO_20448-tor-browser-14-force-all-tests 78 20 Oct 2024, 07:32

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 20:58.292 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:33.384
Before features/support/hooks.rb:269 0.004
Given a computer 0.180
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 32.386
When I start Tails from USB drive "old" with network unplugged 1:54.857
Then the boot device has safe access rights 3.671
And Tails is running from USB drive "old" 0.421
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.108
And udev-watchdog is monitoring the correct device 0.384
And I unplug USB drive "old" 0.209
After features/support/hooks.rb:326 3.682
After features/support/hooks.rb:100 0.014
Tags: @product
2:23.674
Before features/support/hooks.rb:269 0.007
Given a computer 0.503
And I start Tails from USB drive "old" with network unplugged and I login 1:36.418
Then Tails is running from USB drive "old" 0.368
And I create a persistent partition 34.423
And I take note of which tps features are available 1.899
Then a Tails persistence partition exists on USB drive "old" 0.962
And I shutdown Tails and wait for the computer to power off 9.098
After features/support/hooks.rb:326 0.228
After features/support/hooks.rb:100 0.010
Tags: @product
3:3.261
Before features/support/hooks.rb:269 0.006
Given a computer 0.227
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.405
Then Tails is running from USB drive "old" 0.379
And all tps features are active 2.375
When I write some files expected to persist 2.294
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.262
And all persistence configuration files have safe access rights 0.487
And all persistent directories from the old Tails version have safe access rights 2.878
And I take note of which tps features are available 0.511
And I shutdown Tails and wait for the computer to power off 4.643
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.795
After features/support/hooks.rb:326 0.164
After features/support/hooks.rb:100 0.010
Tags: @product
2:54.380
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 21.072
And I log in to a new session 23.171
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.768
And I plug USB drive "to_upgrade" 2.516
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.169
Then the running Tails is installed on USB drive "to_upgrade" 28.993
And I unplug USB drive "to_upgrade" 0.457
And I unplug USB drive "__internal" 0.231
After features/support/hooks.rb:326 2.594
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.123
Before features/support/hooks.rb:269 0.009
Given a computer 0.237
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.376
Then all tps features from the old Tails version are active 1.693
And Tails is running from USB drive "to_upgrade" 0.386
And the boot device has safe access rights 3.371
And the expected persistent files created with the old Tails version are present in the filesystem 1.477
And all persistent directories from the old Tails version have safe access rights 2.579
After features/support/hooks.rb:326 1.100
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:58.541
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.059
And no SquashFS delta is installed 0.185
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.559
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.271
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.462
When the network is plugged 0.065
And Tor is ready 23.520
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.714
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.692
Given I shutdown Tails and wait for the computer to power off 11.045
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.692
Then Tails is running version 6.2~testoverlayfs 0.021
And all tps features are active 2.357
And the file system changes introduced in version 6.2~testoverlayfs are present 0.315
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.320
# 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.304
When the network is plugged 0.085
And Tor is ready 47.095
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.611
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.516
Given I shutdown Tails and wait for the computer to power off 4.381
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.484
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.398
And the file system changes introduced in version 6.3~testoverlayfs are present 0.786
And only the 6.3~testoverlayfs SquashFS delta is installed 0.086
# 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.339
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.288
When the network is plugged 0.077
And Tor is ready 18.547
Then the Upgrader considers the system as up-to-date 0.373
# 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 16.607
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.116
After features/support/hooks.rb:326 0.858
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
40.926
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.195
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.286
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.077
And the signing key used by the Upgrader is outdated 1.015
But a current signing key is available on our website 0.000
When the network is plugged 0.079
And Tor is ready 19.781
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.491
After features/support/hooks.rb:326 0.677
After features/support/hooks.rb:100 0.000