Project Number Date
test_Tails_ISO_20448-tor-browser-14-force-all-tests 36 05 Sep 2024, 18:57

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:18.848 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:17.181
Before features/support/hooks.rb:269 0.006
Given a computer 0.246
And I create a 7200 MiB disk named "old" 0.057
And I plug USB drive "old" 1.060
And I write an old version of the Tails USB image to disk "old" 34.389
When I start Tails from USB drive "old" with network unplugged 1:36.829
Then the boot device has safe access rights 3.451
And Tails is running from USB drive "old" 0.403
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.128
And udev-watchdog is monitoring the correct device 0.328
And I unplug USB drive "old" 0.220
After features/support/hooks.rb:326 3.833
After features/support/hooks.rb:100 0.013
Tags: @product
2:12.809
Before features/support/hooks.rb:269 0.009
Given a computer 0.234
And I start Tails from USB drive "old" with network unplugged and I login 1:24.033
Then Tails is running from USB drive "old" 0.382
And I create a persistent partition 36.794
And I take note of which tps features are available 1.972
Then a Tails persistence partition exists on USB drive "old" 0.933
And I shutdown Tails and wait for the computer to power off 8.458
After features/support/hooks.rb:326 0.132
After features/support/hooks.rb:100 0.009
Tags: @product
2:57.726
Before features/support/hooks.rb:269 0.005
Given a computer 0.298
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.156
Then Tails is running from USB drive "old" 0.492
And all tps features are active 2.434
When I write some files expected to persist 2.069
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.417
And all persistence configuration files have safe access rights 0.485
And all persistent directories from the old Tails version have safe access rights 2.788
And I take note of which tps features are available 2.150
And I shutdown Tails and wait for the computer to power off 4.386
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.046
After features/support/hooks.rb:326 0.104
After features/support/hooks.rb:100 0.009
Tags: @product
2:41.353
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.948
And I log in to a new session 21.652
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.699
And I plug USB drive "to_upgrade" 2.557
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.932
Then the running Tails is installed on USB drive "to_upgrade" 23.134
And I unplug USB drive "to_upgrade" 0.197
And I unplug USB drive "__internal" 0.230
After features/support/hooks.rb:326 2.572
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.447
Before features/support/hooks.rb:269 0.006
Given a computer 0.229
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.358
Then all tps features from the old Tails version are active 1.735
And Tails is running from USB drive "to_upgrade" 0.528
And the boot device has safe access rights 3.555
And the expected persistent files created with the old Tails version are present in the filesystem 1.530
And all persistent directories from the old Tails version have safe access rights 2.508
After features/support/hooks.rb:326 0.794
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:57.205
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 14.341
And no SquashFS delta is installed 0.067
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.626
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.083
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.394
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.535
When the network is plugged 0.335
And Tor is ready 20.793
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.475
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.990
Given I shutdown Tails and wait for the computer to power off 11.618
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.539
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.465
And the file system changes introduced in version 6.2~testoverlayfs are present 0.338
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.380
# 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.080
And Tor is ready 19.374
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.082
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.413
Given I shutdown Tails and wait for the computer to power off 4.378
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.403
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.471
And the file system changes introduced in version 6.3~testoverlayfs are present 0.548
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.330
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.300
When the network is plugged 0.079
And Tor is ready 19.385
Then the Upgrader considers the system as up-to-date 0.325
# 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.474
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.968
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
51.125
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 25.852
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.365
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the signing key used by the Upgrader is outdated 1.391
But a current signing key is available on our website 0.000
When the network is plugged 0.072
And Tor is ready 16.433
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.940
After features/support/hooks.rb:326 0.703
After features/support/hooks.rb:100 0.000