Project Number Date
test_Tails_ISO_stable 5260 11 Nov 2024, 12:35

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:2.587 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:19.119
Before features/support/hooks.rb:269 0.005
Given a computer 0.185
And I create a 7200 MiB disk named "old" 0.057
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 34.537
When I start Tails from USB drive "old" with network unplugged 1:38.768
Then the boot device has safe access rights 3.480
And Tails is running from USB drive "old" 0.344
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.105
And udev-watchdog is monitoring the correct device 0.319
And I unplug USB drive "old" 0.195
After features/support/hooks.rb:326 3.580
After features/support/hooks.rb:100 0.009
Tags: @product
2:12.723
Before features/support/hooks.rb:269 0.005
Given a computer 0.243
And I start Tails from USB drive "old" with network unplugged and I login 1:27.601
Then Tails is running from USB drive "old" 0.357
And I create a persistent partition 33.292
And I take note of which tps features are available 1.894
Then a Tails persistence partition exists on USB drive "old" 0.845
And I shutdown Tails and wait for the computer to power off 8.487
After features/support/hooks.rb:326 0.213
After features/support/hooks.rb:100 0.010
Tags: @product
2:59.524
Before features/support/hooks.rb:269 0.005
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.246
Then Tails is running from USB drive "old" 1.106
And all tps features are active 1.998
When I write some files expected to persist 1.885
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.369
And all persistence configuration files have safe access rights 0.520
And all persistent directories from the old Tails version have safe access rights 2.531
And I take note of which tps features are available 0.670
And I shutdown Tails and wait for the computer to power off 4.060
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.933
After features/support/hooks.rb:326 0.142
After features/support/hooks.rb:100 0.009
Tags: @product
2:35.560
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.377
And I log in to a new session 20.704
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.836
And I plug USB drive "to_upgrade" 2.543
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.959
Then the running Tails is installed on USB drive "to_upgrade" 23.667
And I unplug USB drive "to_upgrade" 0.246
And I unplug USB drive "__internal" 0.224
After features/support/hooks.rb:326 6.777
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.659
Before features/support/hooks.rb:269 0.008
Given a computer 0.202
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.579
Then all tps features from the old Tails version are active 1.652
And Tails is running from USB drive "to_upgrade" 0.368
And the boot device has safe access rights 3.418
And the expected persistent files created with the old Tails version are present in the filesystem 1.501
And all persistent directories from the old Tails version have safe access rights 2.938
After features/support/hooks.rb:326 1.018
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
6:51.198
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 14.873
And no SquashFS delta is installed 0.093
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.353
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.306
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.469
When the network is plugged 0.083
And Tor is ready 21.720
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.768
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.014
Given I shutdown Tails and wait for the computer to power off 11.158
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.099
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 2.766
And the file system changes introduced in version 6.2~testoverlayfs are present 0.372
And only the 6.2~testoverlayfs SquashFS delta is installed 0.096
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.392
# 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.374
When the network is plugged 0.103
And Tor is ready 20.858
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.954
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.492
Given I shutdown Tails and wait for the computer to power off 4.507
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.341
Then Tails is running version 6.3~testoverlayfs 0.020
And all tps features are active 2.037
And the file system changes introduced in version 6.3~testoverlayfs are present 0.560
And only the 6.3~testoverlayfs SquashFS delta is installed 0.082
# 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.451
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.282
When the network is plugged 0.084
And Tor is ready 20.306
Then the Upgrader considers the system as up-to-date 0.307
# 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 18.673
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.106
After features/support/hooks.rb:326 0.689
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
39.800
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 11.362
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.481
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the signing key used by the Upgrader is outdated 0.878
But a current signing key is available on our website 0.000
When the network is plugged 0.071
And Tor is ready 20.174
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.762
After features/support/hooks.rb:326 0.736
After features/support/hooks.rb:100 0.000