Project Number Date
test_Tails_ISO_devel 3618 21 Dec 2024, 12:32

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:13.274 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:58.086
Before features/support/hooks.rb:269 0.005
Given a computer 0.202
And I create a 7200 MiB disk named "old" 0.061
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 30.471
When I start Tails from USB drive "old" with network unplugged 1:22.355
Then the boot device has safe access rights 2.941
And Tails is running from USB drive "old" 0.319
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.110
And udev-watchdog is monitoring the correct device 0.311
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:326 3.534
After features/support/hooks.rb:100 0.023
Tags: @product
2:4.483
Before features/support/hooks.rb:269 0.006
Given a computer 0.241
And I start Tails from USB drive "old" with network unplugged and I login 1:23.072
Then Tails is running from USB drive "old" 0.338
And I create a persistent partition 30.276
And I take note of which tps features are available 1.315
Then a Tails persistence partition exists on USB drive "old" 0.844
And I shutdown Tails and wait for the computer to power off 8.394
After features/support/hooks.rb:326 0.162
After features/support/hooks.rb:100 0.008
Tags: @product
2:57.783
Before features/support/hooks.rb:269 0.004
Given a computer 0.201
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.920
Then Tails is running from USB drive "old" 1.738
And all tps features are active 2.077
When I write some files expected to persist 4.016
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.203
And all persistence configuration files have safe access rights 1.634
And all persistent directories from the old Tails version have safe access rights 2.453
And I take note of which tps features are available 0.429
And I shutdown Tails and wait for the computer to power off 4.156
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.952
After features/support/hooks.rb:326 0.154
After features/support/hooks.rb:100 0.010
Tags: @product
2:32.243
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 11.015
And I log in to a new session 19.025
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.568
And I plug USB drive "to_upgrade" 2.409
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.859
Then the running Tails is installed on USB drive "to_upgrade" 23.933
And I unplug USB drive "to_upgrade" 0.211
And I unplug USB drive "__internal" 0.219
After features/support/hooks.rb:326 2.188
After features/support/hooks.rb:100 0.000
Tags: @product
2:11.745
Before features/support/hooks.rb:269 0.006
Given a computer 0.200
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.582
Then all tps features from the old Tails version are active 1.650
And Tails is running from USB drive "to_upgrade" 0.319
And the boot device has safe access rights 3.243
And the expected persistent files created with the old Tails version are present in the filesystem 1.368
And all persistent directories from the old Tails version have safe access rights 2.380
After features/support/hooks.rb:326 0.805
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:31.902
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.403
And no SquashFS delta is installed 0.100
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.581
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.321
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.426
When the network is plugged 0.093
And Tor is ready 21.756
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.773
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.337
Given I shutdown Tails and wait for the computer to power off 1:18.819
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.256
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.187
And the file system changes introduced in version 6.2~testoverlayfs are present 0.384
And only the 6.2~testoverlayfs SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.312
# 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.333
When the network is plugged 0.088
And Tor is ready 20.377
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.216
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.687
Given I shutdown Tails and wait for the computer to power off 4.335
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.205
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.880
And the file system changes introduced in version 6.3~testoverlayfs are present 0.435
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.292
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.263
When the network is plugged 0.075
And Tor is ready 18.866
Then the Upgrader considers the system as up-to-date 0.347
# 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.321
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.181
After features/support/hooks.rb:326 0.714
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
57.030
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 9.613
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.490
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the signing key used by the Upgrader is outdated 0.740
But a current signing key is available on our website 0.000
When the network is plugged 0.106
And Tor is ready 45.461
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.571
After features/support/hooks.rb:326 0.627
After features/support/hooks.rb:100 0.000