Project Number Date
test_Tails_ISO_devel 3736 13 Mar 2025, 10:09

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:14.406 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:10.662
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.188
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 30.564
When I start Tails from USB drive "old" with network unplugged 1:34.641
Then the boot device has safe access rights 3.180
And Tails is running from USB drive "old" 0.326
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.305
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:330 7.044
After features/support/hooks.rb:100 0.008
Tags: @product
2:12.090
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login 1:29.736
Then Tails is running from USB drive "old" 0.325
And I create a persistent partition 31.348
And I take note of which tps features are available 1.555
Then a Tails persistence partition exists on USB drive "old" 0.756
And I shutdown Tails and wait for the computer to power off 8.181
After features/support/hooks.rb:330 0.205
After features/support/hooks.rb:100 0.008
Tags: @product
2:56.788
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.251
Then Tails is running from USB drive "old" 1.680
And all tps features are active 2.137
When I write some files expected to persist 3.073
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.267
And all persistence configuration files have safe access rights 0.490
And all persistent directories from the old Tails version have safe access rights 3.315
And I take note of which tps features are available 0.468
And I shutdown Tails and wait for the computer to power off 6.550
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.365
After features/support/hooks.rb:330 0.165
After features/support/hooks.rb:100 0.008
Tags: @product
2:26.862
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 9.484
And I log in to a new session 18.048
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.547
And I plug USB drive "to_upgrade" 2.411
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.386
Then the running Tails is installed on USB drive "to_upgrade" 22.593
And I unplug USB drive "to_upgrade" 0.196
And I unplug USB drive "__internal" 0.193
After features/support/hooks.rb:330 3.607
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.064
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.202
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.994
Then all tps features from the old Tails version are active 1.663
And Tails is running from USB drive "to_upgrade" 0.416
And the boot device has safe access rights 2.982
And the expected persistent files created with the old Tails version are present in the filesystem 1.386
And all persistent directories from the old Tails version have safe access rights 2.419
After features/support/hooks.rb:330 1.433
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
6:38.998
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.260
And no SquashFS delta is installed 0.095
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.335
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.548
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.524
When the network is plugged 0.068
And Tor is ready 21.361
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.607
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.898
Given I shutdown Tails and wait for the computer to power off 10.566
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.048
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.207
And the file system changes introduced in version 6.2~testoverlayfs are present 0.294
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.279
# 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.295
When the network is plugged 0.083
And Tor is ready 19.456
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.229
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.928
Given I shutdown Tails and wait for the computer to power off 4.347
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.870
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.977
And the file system changes introduced in version 6.3~testoverlayfs are present 0.516
And only the 6.3~testoverlayfs SquashFS delta is installed 0.108
# 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.475
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.395
When the network is plugged 0.067
And Tor is ready 19.055
Then the Upgrader considers the system as up-to-date 0.318
# 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 16.497
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.126
After features/support/hooks.rb:330 0.713
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
36.938
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.564
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.317
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 0.056
But a current signing key is available on our website 0.000
When the network is plugged 0.122
And Tor is ready 20.615
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.198
After features/support/hooks.rb:330 0.808
After features/support/hooks.rb:100 0.000