Project Number Date
test_Tails_ISO_devel 4105 07 Dec 2025, 09:55

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 15:3.633 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:2.629
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.238
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.041
And I write an old version of the Tails USB image to disk "old" 31.750
When I start Tails from USB drive "old" with network unplugged 1:25.195
Then the boot device has safe access rights 3.446
And Tails is running from USB drive "old" 0.321
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.066
And udev-watchdog is monitoring the correct device 0.270
And I unplug USB drive "old" 0.197
After features/support/hooks.rb:331 3.771
After features/support/hooks.rb:100 0.009
Tags: @product
2:0.966
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.164
And I start Tails from USB drive "old" with network unplugged and I login 1:25.552
Then Tails is running from USB drive "old" 0.614
And I create a persistent partition 29.285
And I take note of which tps features are available 1.271
Then a Tails persistence partition exists on USB drive "old" 0.877
And I shutdown Tails and wait for the computer to power off 3.199
After features/support/hooks.rb:331 0.610
After features/support/hooks.rb:100 0.011
Tags: @product
2:10.325
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:36.171
Then Tails is running from USB drive "old" 0.686
And all tps features are active 1.734
When I write some files expected to persist 1.445
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.226
And all persistence configuration files have safe access rights 0.344
And all persistent directories from the old Tails version have safe access rights 2.332
And I take note of which tps features are available 0.479
And I shutdown Tails and wait for the computer to power off 8.043
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.676
After features/support/hooks.rb:331 0.157
After features/support/hooks.rb:100 0.008
Tags: @product
2:35.156
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 12.614
And I log in to a new session 14.881
And I clone USB drive "old" to a new USB drive "to_upgrade" 6.404
And I plug USB drive "to_upgrade" 2.599
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.262
Then the running Tails is installed on USB drive "to_upgrade" 20.975
And I unplug USB drive "to_upgrade" 0.213
And I unplug USB drive "__internal" 0.204
After features/support/hooks.rb:331 3.680
After features/support/hooks.rb:100 0.000
Tags: @product
1:27.046
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.163
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:17.053
Then all tps features from the old Tails version are active 1.700
And Tails is running from USB drive "to_upgrade" 0.360
And the boot device has safe access rights 3.564
And the expected persistent files created with the old Tails version are present in the filesystem 1.574
And all persistent directories from the old Tails version have safe access rights 2.628
After features/support/hooks.rb:331 0.917
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
4:22.205
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.908
And no SquashFS delta is installed 0.093
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.256
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.088
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.273
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.429
When the network is plugged 0.081
And Tor is ready 14.438
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.401
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.804
Given I shutdown Tails and wait for the computer to power off 9.677
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:21.425
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.572
And the file system changes introduced in version 6.2~testoverlayfs are present 0.290
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.170
# 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.273
When the network is plugged 0.055
And Tor is ready 12.273
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.746
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.454
Given I shutdown Tails and wait for the computer to power off 8.131
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.599
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.681
And the file system changes introduced in version 6.3~testoverlayfs are present 0.476
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.168
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.266
When the network is plugged 0.065
And Tor is ready 13.285
Then the Upgrader considers the system as up-to-date 0.185
# 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.900
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.559
After features/support/hooks.rb:331 0.955
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
25.302
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.046
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.372
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.067
And Tor is ready 12.045
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.630
After features/support/hooks.rb:331 1.512
After features/support/hooks.rb:100 0.000