Project Number Date
test_Tails_ISO_devel 3690 14 Feb 2025, 10:04

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:17.462 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:6.110
Before features/support/hooks.rb:269 0.004
Given a computer 0.195
And I create a 7200 MiB disk named "old" 0.055
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 29.042
When I start Tails from USB drive "old" with network unplugged 1:31.936
Then the boot device has safe access rights 2.912
And Tails is running from USB drive "old" 0.314
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.083
And udev-watchdog is monitoring the correct device 0.285
And I unplug USB drive "old" 0.176
After features/support/hooks.rb:326 8.491
After features/support/hooks.rb:100 0.009
Tags: @product
2:7.425
Before features/support/hooks.rb:269 0.005
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login 1:23.684
Then Tails is running from USB drive "old" 0.347
And I create a persistent partition 32.732
And I take note of which tps features are available 1.455
Then a Tails persistence partition exists on USB drive "old" 0.783
And I shutdown Tails and wait for the computer to power off 8.235
After features/support/hooks.rb:326 0.222
After features/support/hooks.rb:100 0.009
Tags: @product
2:58.155
Before features/support/hooks.rb:269 0.005
Given a computer 0.179
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.744
Then Tails is running from USB drive "old" 1.109
And all tps features are active 2.185
When I write some files expected to persist 2.635
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.208
And all persistence configuration files have safe access rights 0.371
And all persistent directories from the old Tails version have safe access rights 3.156
And I take note of which tps features are available 0.460
And I shutdown Tails and wait for the computer to power off 4.295
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.810
After features/support/hooks.rb:326 0.107
After features/support/hooks.rb:100 0.009
Tags: @product
2:29.050
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.606
And I log in to a new session 18.889
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.809
And I plug USB drive "to_upgrade" 2.377
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.384
Then the running Tails is installed on USB drive "to_upgrade" 19.543
And I unplug USB drive "to_upgrade" 0.224
And I unplug USB drive "__internal" 0.216
After features/support/hooks.rb:326 2.606
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.648
Before features/support/hooks.rb:269 0.006
Given a computer 0.188
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.640
Then all tps features from the old Tails version are active 1.665
And Tails is running from USB drive "to_upgrade" 0.358
And the boot device has safe access rights 3.138
And the expected persistent files created with the old Tails version are present in the filesystem 1.415
And all persistent directories from the old Tails version have safe access rights 2.241
After features/support/hooks.rb:326 1.078
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:39.955
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 25.311
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.339
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.290
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.435
When the network is plugged 0.068
And Tor is ready 21.181
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.474
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.649
Given I shutdown Tails and wait for the computer to power off 8.414
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.483
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.200
And the file system changes introduced in version 6.2~testoverlayfs are present 0.340
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.311
# 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.064
And Tor is ready 20.108
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.239
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.885
Given I shutdown Tails and wait for the computer to power off 4.342
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.848
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.857
And the file system changes introduced in version 6.3~testoverlayfs are present 0.428
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.302
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.239
When the network is plugged 0.069
And Tor is ready 18.194
Then the Upgrader considers the system as up-to-date 0.317
# 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 14.992
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.985
After features/support/hooks.rb:326 0.711
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
37.115
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 9.631
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.327
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.062
But a current signing key is available on our website 0.000
When the network is plugged 0.073
And Tor is ready 21.758
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.205
After features/support/hooks.rb:326 0.886
After features/support/hooks.rb:100 0.000