Project Number Date
test_Tails_ISO_devel 4104 06 Dec 2025, 19:19

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 16:8.310 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:7.678
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.180
And I create a 7200 MiB disk named "old" 0.083
And I plug USB drive "old" 1.071
And I write an old version of the Tails USB image to disk "old" 34.605
When I start Tails from USB drive "old" with network unplugged 1:27.015
Then the boot device has safe access rights 3.741
And Tails is running from USB drive "old" 0.368
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.068
And udev-watchdog is monitoring the correct device 0.233
And I unplug USB drive "old" 0.241
After features/support/hooks.rb:331 3.644
After features/support/hooks.rb:100 0.011
Tags: @product
2:8.630
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.240
And I start Tails from USB drive "old" with network unplugged and I login 1:28.254
Then Tails is running from USB drive "old" 0.326
And I create a persistent partition 29.847
And I take note of which tps features are available 1.305
Then a Tails persistence partition exists on USB drive "old" 0.742
And I shutdown Tails and wait for the computer to power off 7.912
After features/support/hooks.rb:331 0.419
After features/support/hooks.rb:100 0.008
Tags: @product
2:15.488
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:40.342
Then Tails is running from USB drive "old" 0.284
And all tps features are active 2.388
When I write some files expected to persist 1.803
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.220
And all persistence configuration files have safe access rights 0.449
And all persistent directories from the old Tails version have safe access rights 2.539
And I take note of which tps features are available 0.664
And I shutdown Tails and wait for the computer to power off 7.706
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.905
After features/support/hooks.rb:331 0.523
After features/support/hooks.rb:100 0.010
Tags: @product
2:44.536
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.308
And I log in to a new session 17.081
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.534
And I plug USB drive "to_upgrade" 2.362
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:46.044
Then the running Tails is installed on USB drive "to_upgrade" 23.843
And I unplug USB drive "to_upgrade" 0.170
And I unplug USB drive "__internal" 0.191
After features/support/hooks.rb:331 4.130
After features/support/hooks.rb:100 0.000
Tags: @product
1:32.141
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.213
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:21.424
Then all tps features from the old Tails version are active 2.369
And Tails is running from USB drive "to_upgrade" 0.400
And the boot device has safe access rights 4.054
And the expected persistent files created with the old Tails version are present in the filesystem 1.382
And all persistent directories from the old Tails version have safe access rights 2.297
After features/support/hooks.rb:331 0.968
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
4:53.776
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.812
And no SquashFS delta is installed 0.105
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.276
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.290
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.439
When the network is plugged 0.069
And Tor is ready 16.570
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.373
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.192
Given I shutdown Tails and wait for the computer to power off 12.878
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:27.248
Then Tails is running version 6.2~testoverlayfs 0.110
And all tps features are active 2.634
And the file system changes introduced in version 6.2~testoverlayfs are present 0.363
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.184
# 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.258
When the network is plugged 0.060
And Tor is ready 12.376
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.832
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.536
Given I shutdown Tails and wait for the computer to power off 8.205
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:24.205
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.599
And the file system changes introduced in version 6.3~testoverlayfs are present 1.067
And only the 6.3~testoverlayfs SquashFS delta is installed 0.157
# 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.202
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.546
When the network is plugged 0.082
And Tor is ready 11.184
Then the Upgrader considers the system as up-to-date 10.666
# 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 6.593
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.520
After features/support/hooks.rb:331 1.034
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
26.058
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.307
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.379
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.096
And the signing key used by the Upgrader is outdated 0.156
But a current signing key is available on our website 0.000
When the network is plugged 0.090
And Tor is ready 13.306
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.721
After features/support/hooks.rb:331 0.972
After features/support/hooks.rb:100 0.000