Project Number Date
test_Tails_ISO_devel 3635 07 Jan 2025, 03:58

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:54.963 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.443
Before features/support/hooks.rb:269 0.006
Given a computer 0.279
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.067
And I write an old version of the Tails USB image to disk "old" 36.469
When I start Tails from USB drive "old" with network unplugged 1:36.851
Then the boot device has safe access rights 3.648
And Tails is running from USB drive "old" 0.389
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.318
And I unplug USB drive "old" 0.194
After features/support/hooks.rb:326 3.812
After features/support/hooks.rb:100 0.010
Tags: @product
2:25.361
Before features/support/hooks.rb:269 0.007
Given a computer 0.270
And I start Tails from USB drive "old" with network unplugged and I login 1:37.726
Then Tails is running from USB drive "old" 0.374
And I create a persistent partition 35.332
And I take note of which tps features are available 1.950
Then a Tails persistence partition exists on USB drive "old" 0.974
And I shutdown Tails and wait for the computer to power off 8.732
After features/support/hooks.rb:326 0.207
After features/support/hooks.rb:100 0.016
Tags: @product
3:7.727
Before features/support/hooks.rb:269 0.013
Given a computer 0.224
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:28.970
Then Tails is running from USB drive "old" 0.489
And all tps features are active 2.404
When I write some files expected to persist 1.920
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.242
And all persistence configuration files have safe access rights 0.409
And all persistent directories from the old Tails version have safe access rights 2.503
And I take note of which tps features are available 0.548
And I shutdown Tails and wait for the computer to power off 4.723
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.291
After features/support/hooks.rb:326 0.102
After features/support/hooks.rb:100 0.010
Tags: @product
2:43.692
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.274
And I log in to a new session 21.782
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.008
And I plug USB drive "to_upgrade" 2.495
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.797
Then the running Tails is installed on USB drive "to_upgrade" 24.844
And I unplug USB drive "to_upgrade" 0.248
And I unplug USB drive "__internal" 0.241
After features/support/hooks.rb:326 2.192
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.759
Before features/support/hooks.rb:269 0.006
Given a computer 0.273
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.901
Then all tps features from the old Tails version are active 1.748
And Tails is running from USB drive "to_upgrade" 0.368
And the boot device has safe access rights 3.844
And the expected persistent files created with the old Tails version are present in the filesystem 1.666
And all persistent directories from the old Tails version have safe access rights 2.956
After features/support/hooks.rb:326 0.816
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:18.324
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.667
And no SquashFS delta is installed 0.329
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.827
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.333
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.451
When the network is plugged 0.079
And Tor is ready 23.545
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.014
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.651
Given I shutdown Tails and wait for the computer to power off 11.105
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.749
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.262
And the file system changes introduced in version 6.2~testoverlayfs are present 0.382
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.405
# 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.433
When the network is plugged 0.069
And Tor is ready 21.356
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.774
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.778
Given I shutdown Tails and wait for the computer to power off 4.402
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.264
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.849
And the file system changes introduced in version 6.3~testoverlayfs are present 0.579
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.320
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.380
When the network is plugged 0.075
And Tor is ready 47.200
Then the Upgrader considers the system as up-to-date 0.316
# 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.358
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.130
After features/support/hooks.rb:326 0.879
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
38.655
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.567
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.539
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.102
And the signing key used by the Upgrader is outdated 0.090
But a current signing key is available on our website 0.000
When the network is plugged 0.069
And Tor is ready 20.314
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.972
After features/support/hooks.rb:326 0.860
After features/support/hooks.rb:100 0.000