Project Number Date
test_Tails_ISO_stable 5214 23 Oct 2024, 13:10

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 19:1.312 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:12.718
Before features/support/hooks.rb:269 0.004
Given a computer 0.179
And I create a 7200 MiB disk named "old" 0.054
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 32.825
When I start Tails from USB drive "old" with network unplugged 1:34.524
Then the boot device has safe access rights 3.086
And Tails is running from USB drive "old" 0.345
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.101
And udev-watchdog is monitoring the correct device 0.301
And I unplug USB drive "old" 0.176
After features/support/hooks.rb:326 7.016
After features/support/hooks.rb:100 0.008
Tags: @product
2:3.979
Before features/support/hooks.rb:269 0.004
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login 1:21.331
Then Tails is running from USB drive "old" 0.306
And I create a persistent partition 31.460
And I take note of which tps features are available 1.532
Then a Tails persistence partition exists on USB drive "old" 0.875
And I shutdown Tails and wait for the computer to power off 8.286
After features/support/hooks.rb:326 0.141
After features/support/hooks.rb:100 0.007
Tags: @product
2:45.367
Before features/support/hooks.rb:269 0.005
Given a computer 0.401
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:8.730
Then Tails is running from USB drive "old" 0.577
And all tps features are active 1.889
When I write some files expected to persist 1.726
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.215
And all persistence configuration files have safe access rights 0.373
And all persistent directories from the old Tails version have safe access rights 2.376
And I take note of which tps features are available 0.430
And I shutdown Tails and wait for the computer to power off 4.304
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.340
After features/support/hooks.rb:326 0.098
After features/support/hooks.rb:100 0.009
Tags: @product
2:28.720
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.956
And I log in to a new session 19.698
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.670
And I plug USB drive "to_upgrade" 2.423
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.357
Then the running Tails is installed on USB drive "to_upgrade" 18.220
And I unplug USB drive "to_upgrade" 0.197
And I unplug USB drive "__internal" 0.196
After features/support/hooks.rb:326 3.721
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.209
Before features/support/hooks.rb:269 0.004
Given a computer 0.197
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.794
Then all tps features from the old Tails version are active 1.638
And Tails is running from USB drive "to_upgrade" 0.343
And the boot device has safe access rights 3.246
And the expected persistent files created with the old Tails version are present in the filesystem 1.577
And all persistent directories from the old Tails version have safe access rights 2.411
After features/support/hooks.rb:326 1.540
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:35.288
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 13.119
And no SquashFS delta is installed 0.334
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.354
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.264
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.459
When the network is plugged 0.067
And Tor is ready 19.206
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.510
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.530
Given I shutdown Tails and wait for the computer to power off 11.017
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.909
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.206
And the file system changes introduced in version 6.2~testoverlayfs are present 0.475
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.560
# 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.355
When the network is plugged 0.091
And Tor is ready 19.715
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.982
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.358
Given I shutdown Tails and wait for the computer to power off 4.256
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.042
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.135
And the file system changes introduced in version 6.3~testoverlayfs are present 0.470
And only the 6.3~testoverlayfs SquashFS delta is installed 0.080
# 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.307
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.387
When the network is plugged 0.094
And Tor is ready 17.528
Then the Upgrader considers the system as up-to-date 10.805
# 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.691
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.801
After features/support/hooks.rb:326 0.768
After features/support/hooks.rb:100 0.083
Tags: @product @automatic_upgrade
37.029
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 9.727
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.411
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the signing key used by the Upgrader is outdated 0.741
But a current signing key is available on our website 0.000
When the network is plugged 0.068
And Tor is ready 19.710
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.294
After features/support/hooks.rb:326 0.685
After features/support/hooks.rb:100 0.000