Project Number Date
test_Tails_ISO_test-suite-options 15 01 Jul 2025, 21:24

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 28:24.143 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:53.207
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.219
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 40.577
When I start Tails from USB drive "old" with network unplugged 2:2.214
Then the boot device has safe access rights 4.052
And Tails is running from USB drive "old" 2.215
And there is no persistence partition on USB drive "old" 0.540
And process "udev-watchdog" is running 0.354
And udev-watchdog is monitoring the correct device 1.401
And I unplug USB drive "old" 0.533
After features/support/hooks.rb:330 4.390
After features/support/hooks.rb:100 0.038
Tags: @product
3:4.860
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.019
Given a computer 0.357
And I start Tails from USB drive "old" with network unplugged and I login 2:1.661
Then Tails is running from USB drive "old" 0.528
And I create a persistent partition 46.247
And I take note of which tps features are available 3.364
Then a Tails persistence partition exists on USB drive "old" 3.160
And I shutdown Tails and wait for the computer to power off 9.539
After features/support/hooks.rb:330 0.187
After features/support/hooks.rb:100 0.012
Tags: @product
4:20.318
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.223
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:19.838
Then Tails is running from USB drive "old" 2.328
And all tps features are active 2.998
When I write some files expected to persist 7.440
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.343
And all persistence configuration files have safe access rights 0.684
And all persistent directories from the old Tails version have safe access rights 3.621
And I take note of which tps features are available 0.447
And I shutdown Tails and wait for the computer to power off 6.438
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 35.953
After features/support/hooks.rb:330 0.154
After features/support/hooks.rb:100 0.009
Tags: @product
3:34.563
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 16.478
And I log in to a new session 26.383
And I clone USB drive "old" to a new USB drive "to_upgrade" 3.007
And I plug USB drive "to_upgrade" 9.599
When I upgrade Tails to USB drive "to_upgrade" by cloning 2:1.022
Then the running Tails is installed on USB drive "to_upgrade" 37.324
And I unplug USB drive "to_upgrade" 0.516
And I unplug USB drive "__internal" 0.229
After features/support/hooks.rb:330 7.717
After features/support/hooks.rb:100 0.000
Tags: @product
3:26.540
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.236
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:10.029
Then all tps features from the old Tails version are active 3.277
And Tails is running from USB drive "to_upgrade" 0.421
And the boot device has safe access rights 4.202
And the expected persistent files created with the old Tails version are present in the filesystem 2.159
And all persistent directories from the old Tails version have safe access rights 6.213
After features/support/hooks.rb:330 2.769
After features/support/hooks.rb:100 0.029
Tags: @product @automatic_upgrade
10:3.469
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.034
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.396
And no SquashFS delta is installed 1.930
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.297
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.206
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.789
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.976
When the network is plugged 0.213
And Tor is ready 25.007
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 15.568
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 19.696
Given I shutdown Tails and wait for the computer to power off 10.491
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:9.529
Then Tails is running version 6.2~testoverlayfs 0.062
And all tps features are active 3.322
And the file system changes introduced in version 6.2~testoverlayfs are present 0.316
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.325
# 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.310
When the network is plugged 0.065
And Tor is ready 38.683
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.356
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 17.142
Given I shutdown Tails and wait for the computer to power off 13.696
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:54.435
Then Tails is running version 6.3~testoverlayfs 0.514
And all tps features are active 5.930
And the file system changes introduced in version 6.3~testoverlayfs are present 0.968
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.337
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.285
When the network is plugged 0.065
And Tor is ready 25.559
Then the Upgrader considers the system as up-to-date 0.393
# 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 30.122
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 3.317
After features/support/hooks.rb:330 0.963
After features/support/hooks.rb:100 0.028
Tags: @product @automatic_upgrade
1:1.184
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 27.167
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.315
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.111
And the signing key used by the Upgrader is outdated 0.076
But a current signing key is available on our website 0.000
When the network is plugged 0.083
And Tor is ready 28.657
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.772
After features/support/hooks.rb:330 0.860
After features/support/hooks.rb:100 0.000