Project Number Date
test_Tails_ISO_stable 5407 21 Jan 2025, 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 18:30.535 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.128
Before features/support/hooks.rb:269 0.004
Given a computer 0.185
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 29.102
When I start Tails from USB drive "old" with network unplugged 1:23.838
Then the boot device has safe access rights 2.953
And Tails is running from USB drive "old" 0.330
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.083
And udev-watchdog is monitoring the correct device 0.300
And I unplug USB drive "old" 0.175
After features/support/hooks.rb:326 6.851
After features/support/hooks.rb:100 0.008
Tags: @product
2:11.409
Before features/support/hooks.rb:269 0.005
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login 1:29.651
Then Tails is running from USB drive "old" 0.332
And I create a persistent partition 30.575
And I take note of which tps features are available 1.469
Then a Tails persistence partition exists on USB drive "old" 0.771
And I shutdown Tails and wait for the computer to power off 8.423
After features/support/hooks.rb:326 0.166
After features/support/hooks.rb:100 0.008
Tags: @product
2:50.598
Before features/support/hooks.rb:269 0.005
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.622
Then Tails is running from USB drive "old" 1.175
And all tps features are active 1.873
When I write some files expected to persist 1.732
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.262
And all persistence configuration files have safe access rights 0.535
And all persistent directories from the old Tails version have safe access rights 2.348
And I take note of which tps features are available 0.431
And I shutdown Tails and wait for the computer to power off 4.263
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.149
After features/support/hooks.rb:326 0.158
After features/support/hooks.rb:100 0.009
Tags: @product
2:26.442
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 10.012
And I log in to a new session 17.502
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.565
And I plug USB drive "to_upgrade" 2.411
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.327
Then the running Tails is installed on USB drive "to_upgrade" 20.217
And I unplug USB drive "to_upgrade" 0.201
And I unplug USB drive "__internal" 0.205
After features/support/hooks.rb:326 2.067
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.564
Before features/support/hooks.rb:269 0.005
Given a computer 0.398
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.146
Then all tps features from the old Tails version are active 1.600
And Tails is running from USB drive "to_upgrade" 0.331
And the boot device has safe access rights 3.035
And the expected persistent files created with the old Tails version are present in the filesystem 1.554
And all persistent directories from the old Tails version have safe access rights 2.497
After features/support/hooks.rb:326 0.705
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:15.448
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.516
And no SquashFS delta is installed 0.091
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.344
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
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.399
When the network is plugged 0.061
And Tor is ready 22.842
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.402
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.640
Given I shutdown Tails and wait for the computer to power off 8.491
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.862
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.223
And the file system changes introduced in version 6.2~testoverlayfs are present 0.289
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.304
# 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.272
When the network is plugged 0.066
And Tor is ready 18.240
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.183
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.758
Given I shutdown Tails and wait for the computer to power off 4.602
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.986
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.000
And the file system changes introduced in version 6.3~testoverlayfs are present 0.447
And only the 6.3~testoverlayfs SquashFS delta is installed 0.088
# 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.283
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.275
When the network is plugged 0.060
And Tor is ready 19.376
Then the Upgrader considers the system as up-to-date 0.388
# 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.389
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.004
After features/support/hooks.rb:326 0.765
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
35.943
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 10.092
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.356
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.088
But a current signing key is available on our website 0.000
When the network is plugged 0.072
And Tor is ready 18.977
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.302
After features/support/hooks.rb:326 0.682
After features/support/hooks.rb:100 0.000