Project Number Date
test_Tails_ISO_20448-tor-browser-14-force-all-tests 84 24 Oct 2024, 07:28

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:53.487 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.131
Before features/support/hooks.rb:269 0.006
Given a computer 0.219
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.061
And I write an old version of the Tails USB image to disk "old" 30.832
When I start Tails from USB drive "old" with network unplugged 1:28.759
Then the boot device has safe access rights 3.158
And Tails is running from USB drive "old" 0.375
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.314
And I unplug USB drive "old" 0.203
After features/support/hooks.rb:326 10.853
After features/support/hooks.rb:100 0.008
Tags: @product
2:14.837
Before features/support/hooks.rb:269 0.006
Given a computer 0.223
And I start Tails from USB drive "old" with network unplugged and I login 1:31.749
Then Tails is running from USB drive "old" 0.364
And I create a persistent partition 31.273
And I take note of which tps features are available 1.703
Then a Tails persistence partition exists on USB drive "old" 0.804
And I shutdown Tails and wait for the computer to power off 8.717
After features/support/hooks.rb:326 0.214
After features/support/hooks.rb:100 0.013
Tags: @product
2:54.608
Before features/support/hooks.rb:269 0.007
Given a computer 0.334
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.916
Then Tails is running from USB drive "old" 0.413
And all tps features are active 2.489
When I write some files expected to persist 2.015
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.249
And all persistence configuration files have safe access rights 0.394
And all persistent directories from the old Tails version have safe access rights 2.564
And I take note of which tps features are available 0.450
And I shutdown Tails and wait for the computer to power off 4.486
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.293
After features/support/hooks.rb:326 0.130
After features/support/hooks.rb:100 0.010
Tags: @product
2:31.069
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 9.696
And I log in to a new session 18.365
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.535
And I plug USB drive "to_upgrade" 2.365
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.388
Then the running Tails is installed on USB drive "to_upgrade" 24.299
And I unplug USB drive "to_upgrade" 0.214
And I unplug USB drive "__internal" 0.203
After features/support/hooks.rb:326 9.117
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.573
Before features/support/hooks.rb:269 0.005
Given a computer 0.182
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.522
Then all tps features from the old Tails version are active 1.774
And Tails is running from USB drive "to_upgrade" 0.389
And the boot device has safe access rights 3.633
And the expected persistent files created with the old Tails version are present in the filesystem 1.560
And all persistent directories from the old Tails version have safe access rights 2.510
After features/support/hooks.rb:326 0.825
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:17.045
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.038
And no SquashFS delta is installed 0.098
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.382
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.352
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.494
When the network is plugged 0.082
And Tor is ready 20.816
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.390
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.603
Given I shutdown Tails and wait for the computer to power off 10.873
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.128
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.252
And the file system changes introduced in version 6.2~testoverlayfs are present 0.293
And only the 6.2~testoverlayfs SquashFS delta is installed 0.076
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.333
# 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.068
And Tor is ready 19.289
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.535
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.922
Given I shutdown Tails and wait for the computer to power off 4.276
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.255
Then Tails is running version 6.3~testoverlayfs 0.023
And all tps features are active 2.159
And the file system changes introduced in version 6.3~testoverlayfs are present 0.530
And only the 6.3~testoverlayfs SquashFS delta is installed 0.056
# 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.308
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.268
When the network is plugged 0.102
And Tor is ready 19.722
Then the Upgrader considers the system as up-to-date 0.335
# 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 14.708
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.921
After features/support/hooks.rb:326 0.830
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
36.221
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.003
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.651
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the signing key used by the Upgrader is outdated 0.817
But a current signing key is available on our website 0.000
When the network is plugged 0.074
And Tor is ready 15.787
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.815
After features/support/hooks.rb:326 0.697
After features/support/hooks.rb:100 0.000