Project Number Date
test_Tails_ISO_devel 3814 15 May 2025, 23: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 19:39.776 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.403
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.275
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 29.966
When I start Tails from USB drive "old" with network unplugged 1:31.835
Then the boot device has safe access rights 3.247
And Tails is running from USB drive "old" 0.333
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.107
And udev-watchdog is monitoring the correct device 0.297
And I unplug USB drive "old" 0.175
After features/support/hooks.rb:330 3.726
After features/support/hooks.rb:100 0.009
Tags: @product
2:13.507
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login 1:30.688
Then Tails is running from USB drive "old" 0.376
And I create a persistent partition 31.346
And I take note of which tps features are available 1.754
Then a Tails persistence partition exists on USB drive "old" 0.825
And I shutdown Tails and wait for the computer to power off 8.322
After features/support/hooks.rb:330 0.145
After features/support/hooks.rb:100 0.008
Tags: @product
2:55.028
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.179
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.971
Then Tails is running from USB drive "old" 0.355
And all tps features are active 1.899
When I write some files expected to persist 1.814
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.234
And all persistence configuration files have safe access rights 0.397
And all persistent directories from the old Tails version have safe access rights 2.505
And I take note of which tps features are available 0.391
And I shutdown Tails and wait for the computer to power off 4.463
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.814
After features/support/hooks.rb:330 0.110
After features/support/hooks.rb:100 0.010
Tags: @product
2:37.293
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 without a persistent partition and stopped at Tails Greeter's login screen 10.950
And I log in to a new session 19.717
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.244
And I plug USB drive "to_upgrade" 2.460
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.698
Then the running Tails is installed on USB drive "to_upgrade" 25.822
And I unplug USB drive "to_upgrade" 0.199
And I unplug USB drive "__internal" 0.199
After features/support/hooks.rb:330 2.031
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.333
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.192
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.749
Then all tps features from the old Tails version are active 1.976
And Tails is running from USB drive "to_upgrade" 0.393
And the boot device has safe access rights 3.310
And the expected persistent files created with the old Tails version are present in the filesystem 1.410
And all persistent directories from the old Tails version have safe access rights 2.299
After features/support/hooks.rb:330 1.556
After features/support/hooks.rb:100 0.010
6:49.272
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 11.032
And no SquashFS delta is installed 0.130
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.447
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.301
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.455
When the network is plugged 0.067
And Tor is ready 22.718
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.708
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.513
Given I shutdown Tails and wait for the computer to power off 8.906
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:17.781
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.274
And the file system changes introduced in version 6.2~testoverlayfs are present 0.380
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.332
# 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.319
When the network is plugged 0.068
And Tor is ready 18.702
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.154
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.320
Given I shutdown Tails and wait for the computer to power off 4.446
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.146
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.031
And the file system changes introduced in version 6.3~testoverlayfs are present 0.563
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.325
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.283
When the network is plugged 0.063
And Tor is ready 20.153
Then the Upgrader considers the system as up-to-date 0.316
# 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 15.333
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.767
After features/support/hooks.rb:330 0.735
After features/support/hooks.rb:100 0.019
38.937
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 9.629
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.398
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the signing key used by the Upgrader is outdated 0.105
But a current signing key is available on our website 0.000
When the network is plugged 0.088
And Tor is ready 20.627
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.020
After features/support/hooks.rb:330 0.686
After features/support/hooks.rb:100 0.000