Project Number Date
test_Tails_ISO_devel 3863 11 Jun 2025, 13:36

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 22:52.637 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:35.474
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.192
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.059
And I write an old version of the Tails USB image to disk "old" 32.316
When I start Tails from USB drive "old" with network unplugged 1:57.474
Then the boot device has safe access rights 3.358
And Tails is running from USB drive "old" 0.331
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.106
And udev-watchdog is monitoring the correct device 0.316
And I unplug USB drive "old" 0.191
After features/support/hooks.rb:330 3.804
After features/support/hooks.rb:100 0.009
Tags: @product
2:22.117
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.213
And I start Tails from USB drive "old" with network unplugged and I login 1:36.302
Then Tails is running from USB drive "old" 0.454
And I create a persistent partition 33.044
And I take note of which tps features are available 2.354
Then a Tails persistence partition exists on USB drive "old" 0.949
And I shutdown Tails and wait for the computer to power off 8.798
After features/support/hooks.rb:330 0.176
After features/support/hooks.rb:100 0.010
Tags: @product
3:8.648
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:27.440
Then Tails is running from USB drive "old" 0.471
And all tps features are active 2.642
When I write some files expected to persist 2.251
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.351
And all persistence configuration files have safe access rights 0.471
And all persistent directories from the old Tails version have safe access rights 3.146
And I take note of which tps features are available 0.515
And I shutdown Tails and wait for the computer to power off 6.299
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.860
After features/support/hooks.rb:330 0.164
After features/support/hooks.rb:100 0.012
Tags: @product
2:36.947
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 13.665
And I log in to a new session 20.322
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.002
And I plug USB drive "to_upgrade" 2.413
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.241
Then the running Tails is installed on USB drive "to_upgrade" 21.793
And I unplug USB drive "to_upgrade" 0.256
And I unplug USB drive "__internal" 0.250
After features/support/hooks.rb:330 2.327
After features/support/hooks.rb:100 0.000
Tags: @product
2:32.291
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.265
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:20.659
Then all tps features from the old Tails version are active 1.909
And Tails is running from USB drive "to_upgrade" 0.438
And the boot device has safe access rights 4.165
And the expected persistent files created with the old Tails version are present in the filesystem 1.947
And all persistent directories from the old Tails version have safe access rights 2.904
After features/support/hooks.rb:330 1.409
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
8:42.679
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.226
And no SquashFS delta is installed 0.396
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.597
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.347
And the file system changes introduced in version 6.3~testoverlayfs are not present 1.629
When the network is plugged 0.361
And Tor is ready 23.161
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.740
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.013
Given I shutdown Tails and wait for the computer to power off 1:30.927
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.246
Then Tails is running version 6.2~testoverlayfs 0.026
And all tps features are active 3.348
And the file system changes introduced in version 6.2~testoverlayfs are present 0.394
And only the 6.2~testoverlayfs SquashFS delta is installed 0.088
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.346
# 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.492
When the network is plugged 0.285
And Tor is ready 20.781
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.024
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.005
Given I shutdown Tails and wait for the computer to power off 7.109
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:17.037
Then Tails is running version 6.3~testoverlayfs 0.034
And all tps features are active 4.111
And the file system changes introduced in version 6.3~testoverlayfs are present 0.820
And only the 6.3~testoverlayfs SquashFS delta is installed 0.086
# 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.398
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.438
When the network is plugged 0.239
And Tor is ready 22.712
Then the Upgrader considers the system as up-to-date 0.402
# 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 20.848
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.932
After features/support/hooks.rb:330 1.056
After features/support/hooks.rb:100 0.028
Tags: @product @automatic_upgrade
54.479
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.679
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.631
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.097
And the signing key used by the Upgrader is outdated 0.103
But a current signing key is available on our website 0.000
When the network is plugged 0.118
And Tor is ready 27.554
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 11.293
After features/support/hooks.rb:330 1.261
After features/support/hooks.rb:100 0.000