Project Number Date
test_Tails_ISO_stable 4718 14 Mar 2024, 12:19

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:31.391 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
1:49.090
Before features/support/hooks.rb:245 0.005
Given a computer 0.249
And I create a 7200 MiB disk named "old" 0.054
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 20.102
When I start Tails from USB drive "old" with network unplugged 1:22.032
Then the boot device has safe access rights 2.979
And Tails is running from USB drive "old" 1.871
And there is no persistence partition on USB drive "old" 0.085
And process "udev-watchdog" is running 0.107
And udev-watchdog is monitoring the correct device 0.331
And I unplug USB drive "old" 0.220
After features/support/hooks.rb:291 6.862
After features/support/hooks.rb:75 0.011
Tags: @product
2:6.869
Before features/support/hooks.rb:245 0.008
Given a computer 0.218
And I start Tails from USB drive "old" with network unplugged and I login 1:16.081
Then Tails is running from USB drive "old" 0.337
And I create a persistent partition 41.556
And I take note of which tps features are available 1.912
Then a Tails persistence partition exists on USB drive "old" 0.741
And I shutdown Tails and wait for the computer to power off 6.021
After features/support/hooks.rb:291 0.185
After features/support/hooks.rb:75 0.008
Tags: @product
2:37.427
Before features/support/hooks.rb:245 0.005
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:9.320
Then Tails is running from USB drive "old" 0.400
And all tps features are active 2.005
When I write some files expected to persist 1.745
# 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.462
And all persistent directories from the old Tails version have safe access rights 2.406
And I take note of which tps features are available 0.413
And I shutdown Tails and wait for the computer to power off 4.023
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.201
After features/support/hooks.rb:291 0.115
After features/support/hooks.rb:75 0.010
Tags: @product
2:30.045
Before features/support/hooks.rb:245 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 12.400
And I log in to a new session 17.036
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.313
And I plug USB drive "to_upgrade" 2.434
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.785
Then the running Tails is installed on USB drive "to_upgrade" 13.660
And I unplug USB drive "to_upgrade" 0.230
And I unplug USB drive "__internal" 0.183
After features/support/hooks.rb:291 3.561
After features/support/hooks.rb:75 0.000
Tags: @product
2:12.499
Before features/support/hooks.rb:245 0.008
Given a computer 0.247
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.501
Then all tps features from the old Tails version are active 1.614
And Tails is running from USB drive "to_upgrade" 0.322
And the boot device has safe access rights 3.082
And the expected persistent files created with the old Tails version are present in the filesystem 1.383
And all persistent directories from the old Tails version have safe access rights 2.346
After features/support/hooks.rb:291 0.706
After features/support/hooks.rb:75 0.008
Tags: @product @automatic_upgrade
6:35.018
Before features/support/hooks.rb:245 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.910
And no SquashFS delta is installed 0.094
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.380
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.325
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.482
When the network is plugged 0.065
And Tor is ready 21.279
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.713
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.091
Given I shutdown Tails and wait for the computer to power off 9.028
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:17.481
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 4.861
And the file system changes introduced in version 6.2~testoverlayfs are present 0.376
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.313
# 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.296
When the network is plugged 0.045
And Tor is ready 17.786
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.282
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.289
Given I shutdown Tails and wait for the computer to power off 4.019
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.053
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 1.848
And the file system changes introduced in version 6.3~testoverlayfs are present 0.443
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.310
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.290
When the network is plugged 0.072
And Tor is ready 18.293
Then the Upgrader considers the system as up-to-date 0.259
# 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.036
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.056
After features/support/hooks.rb:291 0.941
After features/support/hooks.rb:75 0.055
Tags: @product @automatic_upgrade
40.440
Before features/support/hooks.rb:245 0.013
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.549
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.282
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.081
And the signing key used by the Upgrader is outdated 0.968
But a current signing key is available on our website 0.000
When the network is plugged 0.034
And Tor is ready 19.921
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.602
After features/support/hooks.rb:291 0.640
After features/support/hooks.rb:75 0.000