Project Number Date
test_Tails_ISO_stable 5459 15 Feb 2025, 08:55

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:59.604 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.363
Before features/support/hooks.rb:269 0.003
Given a computer 0.181
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 29.661
When I start Tails from USB drive "old" with network unplugged 1:31.162
Then the boot device has safe access rights 3.251
And Tails is running from USB drive "old" 0.314
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.334
And I unplug USB drive "old" 0.179
After features/support/hooks.rb:326 3.504
After features/support/hooks.rb:100 0.012
Tags: @product
2:7.406
Before features/support/hooks.rb:269 0.005
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login 1:24.254
Then Tails is running from USB drive "old" 0.366
And I create a persistent partition 31.747
And I take note of which tps features are available 1.527
Then a Tails persistence partition exists on USB drive "old" 0.894
And I shutdown Tails and wait for the computer to power off 8.434
After features/support/hooks.rb:326 0.251
After features/support/hooks.rb:100 0.018
Tags: @product
2:51.095
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 with persistence enabled 2:12.814
Then Tails is running from USB drive "old" 0.953
And all tps features are active 2.067
When I write some files expected to persist 2.110
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.255
And all persistence configuration files have safe access rights 0.553
And all persistent directories from the old Tails version have safe access rights 3.070
And I take note of which tps features are available 0.454
And I shutdown Tails and wait for the computer to power off 4.244
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.384
After features/support/hooks.rb:326 0.104
After features/support/hooks.rb:100 0.008
Tags: @product
2:27.413
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 11.240
And I log in to a new session 19.825
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.744
And I plug USB drive "to_upgrade" 2.535
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.126
Then the running Tails is installed on USB drive "to_upgrade" 18.521
And I unplug USB drive "to_upgrade" 0.212
And I unplug USB drive "__internal" 0.207
After features/support/hooks.rb:326 0.928
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.083
Before features/support/hooks.rb:269 0.006
Given a computer 0.193
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.347
Then all tps features from the old Tails version are active 1.853
And Tails is running from USB drive "to_upgrade" 0.421
And the boot device has safe access rights 3.285
And the expected persistent files created with the old Tails version are present in the filesystem 1.493
And all persistent directories from the old Tails version have safe access rights 2.489
After features/support/hooks.rb:326 0.966
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:33.641
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 11.647
And no SquashFS delta is installed 0.193
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.423
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.806
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.456
When the network is plugged 0.138
And Tor is ready 23.085
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.979
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.584
Given I shutdown Tails and wait for the computer to power off 1:21.176
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.702
Then Tails is running version 6.2~testoverlayfs 0.028
And all tps features are active 2.375
And the file system changes introduced in version 6.2~testoverlayfs are present 0.284
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# 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.277
When the network is plugged 0.070
And Tor is ready 18.716
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.738
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.960
Given I shutdown Tails and wait for the computer to power off 4.333
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.830
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.147
And the file system changes introduced in version 6.3~testoverlayfs are present 0.487
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.318
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.271
When the network is plugged 0.071
And Tor is ready 18.906
Then the Upgrader considers the system as up-to-date 0.294
# 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.762
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.046
After features/support/hooks.rb:326 0.723
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
38.599
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.151
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.329
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
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.119
And Tor is ready 21.134
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.726
After features/support/hooks.rb:326 0.650
After features/support/hooks.rb:100 0.000