Project Number Date
test_Tails_ISO_stable 5136 03 Oct 2024, 12:31

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:30.285 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.616
Before features/support/hooks.rb:269 0.006
Given a computer 0.176
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 30.006
When I start Tails from USB drive "old" with network unplugged 1:44.226
Then the boot device has safe access rights 3.102
And Tails is running from USB drive "old" 0.334
And there is no persistence partition on USB drive "old" 0.080
And process "udev-watchdog" is running 0.108
And udev-watchdog is monitoring the correct device 0.302
And I unplug USB drive "old" 0.184
After features/support/hooks.rb:326 3.732
After features/support/hooks.rb:100 0.009
Tags: @product
2:21.215
Before features/support/hooks.rb:269 0.005
Given a computer 0.248
And I start Tails from USB drive "old" with network unplugged and I login 1:33.906
Then Tails is running from USB drive "old" 0.382
And I create a persistent partition 35.945
And I take note of which tps features are available 1.543
Then a Tails persistence partition exists on USB drive "old" 0.834
And I shutdown Tails and wait for the computer to power off 8.353
After features/support/hooks.rb:326 0.137
After features/support/hooks.rb:100 0.009
Tags: @product
2:50.025
Before features/support/hooks.rb:269 0.004
Given a computer 0.174
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.107
Then Tails is running from USB drive "old" 1.488
And all tps features are active 1.870
When I write some files expected to persist 1.559
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.211
And all persistence configuration files have safe access rights 0.528
And all persistent directories from the old Tails version have safe access rights 4.367
And I take note of which tps features are available 0.385
And I shutdown Tails and wait for the computer to power off 4.324
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.007
After features/support/hooks.rb:326 0.103
After features/support/hooks.rb:100 0.009
Tags: @product
2:30.284
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.300
And I log in to a new session 18.560
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.720
And I plug USB drive "to_upgrade" 2.475
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.001
Then the running Tails is installed on USB drive "to_upgrade" 22.834
And I unplug USB drive "to_upgrade" 0.195
And I unplug USB drive "__internal" 0.195
After features/support/hooks.rb:326 6.994
After features/support/hooks.rb:100 0.000
Tags: @product
2:9.228
Before features/support/hooks.rb:269 0.007
Given a computer 0.177
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:0.216
Then all tps features from the old Tails version are active 1.509
And Tails is running from USB drive "to_upgrade" 0.320
And the boot device has safe access rights 3.057
And the expected persistent files created with the old Tails version are present in the filesystem 1.326
And all persistent directories from the old Tails version have safe access rights 2.620
After features/support/hooks.rb:326 0.937
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:45.772
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.395
And no SquashFS delta is installed 0.169
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.339
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.329
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.435
When the network is plugged 0.067
And Tor is ready 23.067
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.014
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.168
Given I shutdown Tails and wait for the computer to power off 8.547
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.415
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.179
And the file system changes introduced in version 6.2~testoverlayfs are present 0.280
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# 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.305
When the network is plugged 0.076
And Tor is ready 46.251
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.617
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.943
Given I shutdown Tails and wait for the computer to power off 58.009
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.993
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.984
And the file system changes introduced in version 6.3~testoverlayfs are present 0.449
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.311
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.276
When the network is plugged 0.082
And Tor is ready 15.432
Then the Upgrader considers the system as up-to-date 10.725
# 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.219
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.051
After features/support/hooks.rb:326 0.811
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
34.143
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 10.163
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.634
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.799
But a current signing key is available on our website 0.000
When the network is plugged 0.074
And Tor is ready 15.912
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.514
After features/support/hooks.rb:326 1.461
After features/support/hooks.rb:100 0.000