Project Number Date
test_Tails_ISO_stable 5465 17 Feb 2025, 16:49

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 18:53.343 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:5.303
Before features/support/hooks.rb:269 0.004
Given a computer 0.177
And I create a 7200 MiB disk named "old" 0.037
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 31.222
When I start Tails from USB drive "old" with network unplugged 1:28.629
Then the boot device has safe access rights 3.171
And Tails is running from USB drive "old" 0.373
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.081
And udev-watchdog is monitoring the correct device 0.294
And I unplug USB drive "old" 0.191
After features/support/hooks.rb:326 7.024
After features/support/hooks.rb:100 0.009
Tags: @product
2:12.984
Before features/support/hooks.rb:269 0.006
Given a computer 0.204
And I start Tails from USB drive "old" with network unplugged and I login 1:27.645
Then Tails is running from USB drive "old" 0.370
And I create a persistent partition 34.498
And I take note of which tps features are available 1.257
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.233
After features/support/hooks.rb:326 0.224
After features/support/hooks.rb:100 0.009
Tags: @product
2:55.657
Before features/support/hooks.rb:269 0.005
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.035
Then Tails is running from USB drive "old" 0.325
And all tps features are active 1.901
When I write some files expected to persist 2.120
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.209
And all persistence configuration files have safe access rights 0.418
And all persistent directories from the old Tails version have safe access rights 2.357
And I take note of which tps features are available 0.390
And I shutdown Tails and wait for the computer to power off 4.349
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.366
After features/support/hooks.rb:326 0.137
After features/support/hooks.rb:100 0.009
Tags: @product
2:26.383
Before features/support/hooks.rb:269 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 9.671
And I log in to a new session 18.214
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.706
And I plug USB drive "to_upgrade" 2.467
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.821
Then the running Tails is installed on USB drive "to_upgrade" 20.094
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.204
After features/support/hooks.rb:326 2.329
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.268
Before features/support/hooks.rb:269 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 2:11.827
Then all tps features from the old Tails version are active 1.608
And Tails is running from USB drive "to_upgrade" 0.344
And the boot device has safe access rights 3.296
And the expected persistent files created with the old Tails version are present in the filesystem 1.405
And all persistent directories from the old Tails version have safe access rights 2.617
After features/support/hooks.rb:326 1.095
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:14.193
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.784
And no SquashFS delta is installed 0.096
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.011
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.077
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.384
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.429
When the network is plugged 0.064
And Tor is ready 21.449
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.496
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.723
Given I shutdown Tails and wait for the computer to power off 10.792
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.898
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.118
And the file system changes introduced in version 6.2~testoverlayfs are present 0.304
And only the 6.2~testoverlayfs SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.317
# 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.073
And Tor is ready 20.422
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.153
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.207
Given I shutdown Tails and wait for the computer to power off 4.174
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.515
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 1.999
And the file system changes introduced in version 6.3~testoverlayfs are present 0.516
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.347
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.251
When the network is plugged 0.087
And Tor is ready 17.465
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 15.090
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.097
After features/support/hooks.rb:326 0.768
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
37.552
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.376
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.905
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the signing key used by the Upgrader is outdated 0.073
But a current signing key is available on our website 0.000
When the network is plugged 0.070
And Tor is ready 19.505
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.554
After features/support/hooks.rb:326 0.846
After features/support/hooks.rb:100 0.000