Project Number Date
test_Tails_ISO_devel 3669 29 Jan 2025, 02:42

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:4.883 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.428
Before features/support/hooks.rb:269 0.003
Given a computer 0.172
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 33.787
When I start Tails from USB drive "old" with network unplugged 1:38.136
Then the boot device has safe access rights 3.155
And Tails is running from USB drive "old" 0.385
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.106
And udev-watchdog is monitoring the correct device 0.317
And I unplug USB drive "old" 0.191
After features/support/hooks.rb:326 23.068
After features/support/hooks.rb:100 0.007
Tags: @product
2:21.251
Before features/support/hooks.rb:269 0.003
Given a computer 0.169
And I start Tails from USB drive "old" with network unplugged and I login 1:33.298
Then Tails is running from USB drive "old" 0.322
And I create a persistent partition 36.218
And I take note of which tps features are available 1.480
Then a Tails persistence partition exists on USB drive "old" 0.953
And I shutdown Tails and wait for the computer to power off 8.808
After features/support/hooks.rb:326 0.160
After features/support/hooks.rb:100 0.008
Tags: @product
2:51.394
Before features/support/hooks.rb:269 0.004
Given a computer 0.224
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.408
Then Tails is running from USB drive "old" 0.785
And all tps features are active 2.077
When I write some files expected to persist 1.877
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.412
And all persistence configuration files have safe access rights 0.479
And all persistent directories from the old Tails version have safe access rights 2.700
And I take note of which tps features are available 0.444
And I shutdown Tails and wait for the computer to power off 4.302
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.682
After features/support/hooks.rb:326 0.099
After features/support/hooks.rb:100 0.005
Tags: @product
2:45.916
Before features/support/hooks.rb:269 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.465
And I log in to a new session 32.102
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.060
And I plug USB drive "to_upgrade" 2.387
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.439
Then the running Tails is installed on USB drive "to_upgrade" 20.014
And I unplug USB drive "to_upgrade" 0.216
And I unplug USB drive "__internal" 0.228
After features/support/hooks.rb:326 3.555
After features/support/hooks.rb:100 0.000
Tags: @product
2:23.612
Before features/support/hooks.rb:269 0.004
Given a computer 0.176
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.370
Then all tps features from the old Tails version are active 1.886
And Tails is running from USB drive "to_upgrade" 0.330
And the boot device has safe access rights 3.506
And the expected persistent files created with the old Tails version are present in the filesystem 1.676
And all persistent directories from the old Tails version have safe access rights 2.665
After features/support/hooks.rb:326 1.068
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:45.330
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.862
And no SquashFS delta is installed 0.096
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.319
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.295
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.441
When the network is plugged 0.084
And Tor is ready 21.991
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.779
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.359
Given I shutdown Tails and wait for the computer to power off 8.469
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.775
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.499
And the file system changes introduced in version 6.2~testoverlayfs are present 0.583
And only the 6.2~testoverlayfs SquashFS delta is installed 0.127
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.353
# 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.379
When the network is plugged 0.090
And Tor is ready 21.728
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.803
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.605
Given I shutdown Tails and wait for the computer to power off 6.405
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.624
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.433
And the file system changes introduced in version 6.3~testoverlayfs are present 0.503
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.354
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.310
When the network is plugged 0.072
And Tor is ready 17.912
Then the Upgrader considers the system as up-to-date 0.378
# 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.510
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.023
After features/support/hooks.rb:326 0.748
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
39.949
Before features/support/hooks.rb:269 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.733
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.383
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.085
But a current signing key is available on our website 0.000
When the network is plugged 0.101
And Tor is ready 21.123
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.460
After features/support/hooks.rb:326 0.694
After features/support/hooks.rb:100 0.000