Project Number Date
test_Tails_ISO_devel 4077 17 Nov 2025, 13:11

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:16.559 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:59.903
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.289
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 31.963
When I start Tails from USB drive "old" with network unplugged 1:22.841
Then the boot device has safe access rights 2.803
And Tails is running from USB drive "old" 0.283
And there is no persistence partition on USB drive "old" 0.057
And process "udev-watchdog" is running 0.049
And udev-watchdog is monitoring the correct device 0.274
And I unplug USB drive "old" 0.249
After features/support/hooks.rb:331 4.142
After features/support/hooks.rb:100 0.022
Tags: @product
2:4.612
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.167
And I start Tails from USB drive "old" with network unplugged and I login 1:24.646
Then Tails is running from USB drive "old" 0.376
And I create a persistent partition 29.210
And I take note of which tps features are available 1.211
Then a Tails persistence partition exists on USB drive "old" 1.138
And I shutdown Tails and wait for the computer to power off 7.861
After features/support/hooks.rb:331 0.396
After features/support/hooks.rb:100 0.009
Tags: @product
2:8.354
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.219
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:35.080
Then Tails is running from USB drive "old" 0.304
And all tps features are active 1.886
When I write some files expected to persist 1.662
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.278
And all persistence configuration files have safe access rights 0.482
And all persistent directories from the old Tails version have safe access rights 2.182
And I take note of which tps features are available 0.455
And I shutdown Tails and wait for the computer to power off 7.607
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.195
After features/support/hooks.rb:331 0.133
After features/support/hooks.rb:100 0.009
Tags: @product
2:33.369
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 15.360
And I log in to a new session 16.359
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.657
And I plug USB drive "to_upgrade" 2.785
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.609
Then the running Tails is installed on USB drive "to_upgrade" 21.165
And I unplug USB drive "to_upgrade" 0.209
And I unplug USB drive "__internal" 0.222
After features/support/hooks.rb:331 4.117
After features/support/hooks.rb:100 0.000
Tags: @product
1:48.618
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.168
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:39.601
Then all tps features from the old Tails version are active 1.449
And Tails is running from USB drive "to_upgrade" 0.300
And the boot device has safe access rights 3.129
And the expected persistent files created with the old Tails version are present in the filesystem 1.555
And all persistent directories from the old Tails version have safe access rights 2.412
After features/support/hooks.rb:331 0.865
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
5:19.031
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 12.705
And no SquashFS delta is installed 0.097
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.282
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.265
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.467
When the network is plugged 0.051
And Tor is ready 13.815
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.854
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.700
Given I shutdown Tails and wait for the computer to power off 11.221
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:42.633
Then Tails is running version 6.2~testoverlayfs 0.009
And all tps features are active 2.145
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.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.173
# 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.256
When the network is plugged 0.056
And Tor is ready 12.368
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.729
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.472
Given I shutdown Tails and wait for the computer to power off 8.500
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:45.697
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.225
And the file system changes introduced in version 6.3~testoverlayfs are present 0.432
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.160
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.225
When the network is plugged 0.056
And Tor is ready 12.454
Then the Upgrader considers the system as up-to-date 0.209
# 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 13.326
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.905
After features/support/hooks.rb:331 1.187
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
22.669
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.406
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.248
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.059
But a current signing key is available on our website 0.000
When the network is plugged 0.047
And Tor is ready 11.225
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.629
After features/support/hooks.rb:331 0.744
After features/support/hooks.rb:100 0.000