Project Number Date
test_Tails_ISO_stable 5372 07 Jan 2025, 16:15

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:50.168 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.369
Before features/support/hooks.rb:269 0.004
Given a computer 0.210
And I create a 7200 MiB disk named "old" 0.054
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 43.712
When I start Tails from USB drive "old" with network unplugged 1:28.151
Then the boot device has safe access rights 3.161
And Tails is running from USB drive "old" 0.329
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.107
And udev-watchdog is monitoring the correct device 0.328
And I unplug USB drive "old" 0.184
After features/support/hooks.rb:326 7.338
After features/support/hooks.rb:100 0.011
Tags: @product
2:39.555
Before features/support/hooks.rb:269 0.007
Given a computer 0.274
And I start Tails from USB drive "old" with network unplugged and I login 1:49.770
Then Tails is running from USB drive "old" 0.465
And I create a persistent partition 37.113
And I take note of which tps features are available 2.446
Then a Tails persistence partition exists on USB drive "old" 1.015
And I shutdown Tails and wait for the computer to power off 8.469
After features/support/hooks.rb:326 0.150
After features/support/hooks.rb:100 0.008
Tags: @product
3:17.048
Before features/support/hooks.rb:269 0.005
Given a computer 0.253
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:35.896
Then Tails is running from USB drive "old" 0.434
And all tps features are active 2.546
When I write some files expected to persist 2.607
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.251
And all persistence configuration files have safe access rights 0.415
And all persistent directories from the old Tails version have safe access rights 3.325
And I take note of which tps features are available 0.630
And I shutdown Tails and wait for the computer to power off 4.464
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.222
After features/support/hooks.rb:326 0.205
After features/support/hooks.rb:100 0.010
Tags: @product
3:0.161
Before features/support/hooks.rb:269 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 27.885
And I log in to a new session 19.750
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.684
And I plug USB drive "to_upgrade" 2.471
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:43.151
Then the running Tails is installed on USB drive "to_upgrade" 24.754
And I unplug USB drive "to_upgrade" 0.215
And I unplug USB drive "__internal" 0.248
After features/support/hooks.rb:326 3.772
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.863
Before features/support/hooks.rb:269 0.006
Given a computer 0.211
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.065
Then all tps features from the old Tails version are active 1.861
And Tails is running from USB drive "to_upgrade" 0.323
And the boot device has safe access rights 3.361
And the expected persistent files created with the old Tails version are present in the filesystem 1.538
And all persistent directories from the old Tails version have safe access rights 2.500
After features/support/hooks.rb:326 1.077
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
6:35.881
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 11.542
And no SquashFS delta is installed 0.073
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.312
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.409
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.540
When the network is plugged 0.067
And Tor is ready 21.994
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.384
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.022
Given I shutdown Tails and wait for the computer to power off 8.952
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.056
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 3.203
And the file system changes introduced in version 6.2~testoverlayfs are present 0.335
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.307
# 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.258
When the network is plugged 0.088
And Tor is ready 17.970
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.354
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.683
Given I shutdown Tails and wait for the computer to power off 6.645
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.404
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.401
And the file system changes introduced in version 6.3~testoverlayfs are present 0.485
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.302
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.405
When the network is plugged 0.103
And Tor is ready 18.752
Then the Upgrader considers the system as up-to-date 0.420
# 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.003
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.178
After features/support/hooks.rb:326 0.843
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
37.289
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.910
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.461
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the signing key used by the Upgrader is outdated 0.075
But a current signing key is available on our website 0.000
When the network is plugged 0.104
And Tor is ready 18.072
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.597
After features/support/hooks.rb:326 0.696
After features/support/hooks.rb:100 0.000