Project Number Date
test_Tails_ISO_20448-tor-browser-14-force-all-tests 71 09 Oct 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 19:11.166 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:5.292
Before features/support/hooks.rb:269 0.005
Given a computer 0.186
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 30.790
When I start Tails from USB drive "old" with network unplugged 1:29.149
Then the boot device has safe access rights 3.069
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.113
And udev-watchdog is monitoring the correct device 0.278
And I unplug USB drive "old" 0.200
After features/support/hooks.rb:326 3.528
After features/support/hooks.rb:100 0.012
Tags: @product
2:5.870
Before features/support/hooks.rb:269 0.007
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login 1:21.769
Then Tails is running from USB drive "old" 0.382
And I create a persistent partition 32.591
And I take note of which tps features are available 1.509
Then a Tails persistence partition exists on USB drive "old" 0.827
And I shutdown Tails and wait for the computer to power off 8.591
After features/support/hooks.rb:326 0.188
After features/support/hooks.rb:100 0.008
Tags: @product
2:47.480
Before features/support/hooks.rb:269 0.006
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:7.553
Then Tails is running from USB drive "old" 0.943
And all tps features are active 2.716
When I write some files expected to persist 2.373
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.284
And all persistence configuration files have safe access rights 0.442
And all persistent directories from the old Tails version have safe access rights 2.696
And I take note of which tps features are available 0.672
And I shutdown Tails and wait for the computer to power off 4.505
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.098
After features/support/hooks.rb:326 0.123
After features/support/hooks.rb:100 0.010
Tags: @product
2:31.266
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 13.748
And I log in to a new session 19.510
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.716
And I plug USB drive "to_upgrade" 2.480
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.309
Then the running Tails is installed on USB drive "to_upgrade" 17.012
And I unplug USB drive "to_upgrade" 0.197
And I unplug USB drive "__internal" 0.291
After features/support/hooks.rb:326 3.757
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.832
Before features/support/hooks.rb:269 0.010
Given a computer 0.244
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.521
Then all tps features from the old Tails version are active 1.825
And Tails is running from USB drive "to_upgrade" 0.344
And the boot device has safe access rights 3.061
And the expected persistent files created with the old Tails version are present in the filesystem 1.417
And all persistent directories from the old Tails version have safe access rights 2.418
After features/support/hooks.rb:326 0.854
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:40.558
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.659
And no SquashFS delta is installed 0.307
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.253
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.111
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.269
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.448
When the network is plugged 0.081
And Tor is ready 20.575
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.443
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.709
Given I shutdown Tails and wait for the computer to power off 10.866
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:20.295
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.187
And the file system changes introduced in version 6.2~testoverlayfs are present 0.362
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.328
# 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.261
When the network is plugged 0.075
And Tor is ready 20.209
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.285
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.881
Given I shutdown Tails and wait for the computer to power off 4.484
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.028
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.150
And the file system changes introduced in version 6.3~testoverlayfs are present 0.480
And only the 6.3~testoverlayfs SquashFS delta is installed 0.084
# 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.313
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.286
When the network is plugged 0.070
And Tor is ready 18.770
Then the Upgrader considers the system as up-to-date 0.330
# 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.838
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.008
After features/support/hooks.rb:326 1.052
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
39.865
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.457
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.484
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 0.813
But a current signing key is available on our website 0.000
When the network is plugged 0.064
And Tor is ready 20.319
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.675
After features/support/hooks.rb:326 0.775
After features/support/hooks.rb:100 0.000