Project Number Date
test_Tails_ISO_devel 4038 28 Oct 2025, 11:21

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:11.987 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:51.868
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.235
And I create a 7200 MiB disk named "old" 0.060
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 28.366
When I start Tails from USB drive "old" with network unplugged 1:18.305
Then the boot device has safe access rights 2.978
And Tails is running from USB drive "old" 0.329
And there is no persistence partition on USB drive "old" 0.056
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.230
And I unplug USB drive "old" 0.200
After features/support/hooks.rb:331 3.903
After features/support/hooks.rb:100 0.009
Tags: @product
2:3.927
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login 1:25.744
Then Tails is running from USB drive "old" 0.364
And I create a persistent partition 27.761
And I take note of which tps features are available 1.376
Then a Tails persistence partition exists on USB drive "old" 0.754
And I shutdown Tails and wait for the computer to power off 7.729
After features/support/hooks.rb:331 0.582
After features/support/hooks.rb:100 0.010
Tags: @product
2:18.235
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.222
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:43.429
Then Tails is running from USB drive "old" 0.352
And all tps features are active 2.348
When I write some files expected to persist 1.793
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.242
And all persistence configuration files have safe access rights 0.419
And all persistent directories from the old Tails version have safe access rights 2.598
And I take note of which tps features are available 0.595
And I shutdown Tails and wait for the computer to power off 7.587
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.645
After features/support/hooks.rb:331 0.234
After features/support/hooks.rb:100 0.010
Tags: @product
2:32.676
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 without a persistent partition and stopped at Tails Greeter's login screen 12.788
And I log in to a new session 17.508
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.818
And I plug USB drive "to_upgrade" 2.808
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.543
Then the running Tails is installed on USB drive "to_upgrade" 20.789
And I unplug USB drive "to_upgrade" 0.210
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:331 3.870
After features/support/hooks.rb:100 0.000
Tags: @product
1:50.598
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.217
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:41.258
Then all tps features from the old Tails version are active 1.544
And Tails is running from USB drive "to_upgrade" 0.285
And the boot device has safe access rights 3.282
And the expected persistent files created with the old Tails version are present in the filesystem 1.649
And all persistent directories from the old Tails version have safe access rights 2.361
After features/support/hooks.rb:331 0.810
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
5:8.191
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.358
And no SquashFS delta is installed 0.103
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.309
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.090
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.298
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.424
When the network is plugged 0.093
And Tor is ready 14.596
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.757
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.078
Given I shutdown Tails and wait for the computer to power off 11.113
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:42.356
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.334
And the file system changes introduced in version 6.2~testoverlayfs are present 0.275
And only the 6.2~testoverlayfs SquashFS delta is installed 0.058
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.178
# 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.270
When the network is plugged 0.092
And Tor is ready 12.288
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.762
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.802
Given I shutdown Tails and wait for the computer to power off 7.873
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:41.272
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.687
And the file system changes introduced in version 6.3~testoverlayfs are present 0.495
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.162
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.264
When the network is plugged 0.081
And Tor is ready 13.152
Then the Upgrader considers the system as up-to-date 0.272
# 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 5.730
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.460
After features/support/hooks.rb:331 0.949
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
26.489
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 11.323
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.278
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.078
And the signing key used by the Upgrader is outdated 0.073
But a current signing key is available on our website 0.000
When the network is plugged 0.069
And Tor is ready 11.377
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.288
After features/support/hooks.rb:331 0.881
After features/support/hooks.rb:100 0.000