Project Number Date
test_Tails_ISO_20979-pdfarranger 12 07 Jun 2025, 02:39

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:44.363 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:14.041
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.185
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 31.266
When I start Tails from USB drive "old" with network unplugged 1:37.402
Then the boot device has safe access rights 3.107
And Tails is running from USB drive "old" 0.315
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.084
And udev-watchdog is monitoring the correct device 0.305
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:330 6.855
After features/support/hooks.rb:100 0.010
Tags: @product
2:12.255
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login 1:28.050
Then Tails is running from USB drive "old" 0.321
And I create a persistent partition 31.969
And I take note of which tps features are available 2.432
Then a Tails persistence partition exists on USB drive "old" 0.775
And I shutdown Tails and wait for the computer to power off 8.520
After features/support/hooks.rb:330 0.199
After features/support/hooks.rb:100 0.009
Tags: @product
2:52.467
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.005
Then Tails is running from USB drive "old" 1.179
And all tps features are active 2.262
When I write some files expected to persist 2.604
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.213
And all persistence configuration files have safe access rights 0.391
And all persistent directories from the old Tails version have safe access rights 2.930
And I take note of which tps features are available 0.502
And I shutdown Tails and wait for the computer to power off 4.631
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.541
After features/support/hooks.rb:330 0.129
After features/support/hooks.rb:100 0.020
Tags: @product
2:31.955
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.015
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.952
And I log in to a new session 19.137
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.699
And I plug USB drive "to_upgrade" 2.384
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.779
Then the running Tails is installed on USB drive "to_upgrade" 23.528
And I unplug USB drive "to_upgrade" 0.241
And I unplug USB drive "__internal" 0.231
After features/support/hooks.rb:330 3.806
After features/support/hooks.rb:100 0.000
Tags: @product
2:27.100
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.201
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:17.696
Then all tps features from the old Tails version are active 1.627
And Tails is running from USB drive "to_upgrade" 0.323
And the boot device has safe access rights 3.382
And the expected persistent files created with the old Tails version are present in the filesystem 1.371
And all persistent directories from the old Tails version have safe access rights 2.498
After features/support/hooks.rb:330 1.341
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:45.986
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 11.694
And no SquashFS delta is installed 1.156
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.519
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.425
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.415
When the network is plugged 0.131
And Tor is ready 27.813
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.024
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.902
Given I shutdown Tails and wait for the computer to power off 9.111
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.293
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.316
And the file system changes introduced in version 6.2~testoverlayfs are present 0.369
And only the 6.2~testoverlayfs SquashFS delta is installed 0.083
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.418
# 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.258
When the network is plugged 0.068
And Tor is ready 19.683
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.764
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.155
Given I shutdown Tails and wait for the computer to power off 4.516
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.076
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.165
And the file system changes introduced in version 6.3~testoverlayfs are present 0.502
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.317
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.314
When the network is plugged 0.078
And Tor is ready 20.812
Then the Upgrader considers the system as up-to-date 0.369
# 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 16.405
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.656
After features/support/hooks.rb:330 0.724
After features/support/hooks.rb:100 0.032
Tags: @product @automatic_upgrade
40.555
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.067
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.117
And the signing key used by the Upgrader is outdated 0.200
But a current signing key is available on our website 0.000
When the network is plugged 0.091
And Tor is ready 21.581
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.098
After features/support/hooks.rb:330 0.748
After features/support/hooks.rb:100 0.000