Project Number Date
test_Tails_ISO_devel 3692 15 Feb 2025, 09:44

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:0.228 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:7.588
Before features/support/hooks.rb:269 0.006
Given a computer 0.227
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 30.796
When I start Tails from USB drive "old" with network unplugged 1:31.334
Then the boot device has safe access rights 3.132
And Tails is running from USB drive "old" 0.358
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.288
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:326 7.117
After features/support/hooks.rb:100 0.009
Tags: @product
2:9.095
Before features/support/hooks.rb:269 0.006
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login 1:26.614
Then Tails is running from USB drive "old" 0.307
And I create a persistent partition 31.371
And I take note of which tps features are available 1.457
Then a Tails persistence partition exists on USB drive "old" 0.840
And I shutdown Tails and wait for the computer to power off 8.311
After features/support/hooks.rb:326 0.208
After features/support/hooks.rb:100 0.009
Tags: @product
2:56.462
Before features/support/hooks.rb:269 0.005
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.331
Then Tails is running from USB drive "old" 1.190
And all tps features are active 2.045
When I write some files expected to persist 1.702
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.246
And all persistence configuration files have safe access rights 0.409
And all persistent directories from the old Tails version have safe access rights 4.264
And I take note of which tps features are available 0.509
And I shutdown Tails and wait for the computer to power off 4.455
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.112
After features/support/hooks.rb:326 0.135
After features/support/hooks.rb:100 0.009
Tags: @product
2:27.791
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.633
And I log in to a new session 18.969
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.594
And I plug USB drive "to_upgrade" 2.361
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.993
Then the running Tails is installed on USB drive "to_upgrade" 19.806
And I unplug USB drive "to_upgrade" 0.218
And I unplug USB drive "__internal" 0.214
After features/support/hooks.rb:326 6.773
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.073
Before features/support/hooks.rb:269 0.007
Given a computer 0.221
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.800
Then all tps features from the old Tails version are active 1.582
And Tails is running from USB drive "to_upgrade" 0.382
And the boot device has safe access rights 3.483
And the expected persistent files created with the old Tails version are present in the filesystem 1.384
And all persistent directories from the old Tails version have safe access rights 2.218
After features/support/hooks.rb:326 0.752
After features/support/hooks.rb:100 0.035
Tags: @product @automatic_upgrade
6:22.481
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.384
And no SquashFS delta is installed 0.096
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.070
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.318
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.496
When the network is plugged 0.115
And Tor is ready 20.608
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.593
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.508
Given I shutdown Tails and wait for the computer to power off 8.612
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.916
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.176
And the file system changes introduced in version 6.2~testoverlayfs are present 0.271
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.300
# 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.247
When the network is plugged 0.074
And Tor is ready 18.797
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.268
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.420
Given I shutdown Tails and wait for the computer to power off 4.330
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.775
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.049
And the file system changes introduced in version 6.3~testoverlayfs are present 0.474
And only the 6.3~testoverlayfs SquashFS delta is installed 0.092
# 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.301
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.262
When the network is plugged 0.073
And Tor is ready 19.349
Then the Upgrader considers the system as up-to-date 0.302
# 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 17.357
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.139
After features/support/hooks.rb:326 0.748
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
34.734
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.784
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.358
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the signing key used by the Upgrader is outdated 0.075
But a current signing key is available on our website 0.000
When the network is plugged 0.103
And Tor is ready 19.234
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.104
After features/support/hooks.rb:326 0.891
After features/support/hooks.rb:100 0.000