Project Number Date
test_Tails_ISO_devel 3429 17 Jun 2024, 12:53

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:45.663 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.208
Before features/support/hooks.rb:269 0.012
Given a computer 0.215
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 28.507
When I start Tails from USB drive "old" with network unplugged 1:33.516
Then the boot device has safe access rights 2.901
And Tails is running from USB drive "old" 0.327
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.302
And I unplug USB drive "old" 0.182
After features/support/hooks.rb:315 6.863
After features/support/hooks.rb:100 0.009
Tags: @product
2:5.730
Before features/support/hooks.rb:269 0.006
Given a computer 0.223
And I start Tails from USB drive "old" with network unplugged and I login 1:21.329
Then Tails is running from USB drive "old" 0.375
And I create a persistent partition 32.860
And I take note of which tps features are available 1.550
Then a Tails persistence partition exists on USB drive "old" 0.839
And I shutdown Tails and wait for the computer to power off 8.552
After features/support/hooks.rb:315 0.195
After features/support/hooks.rb:100 0.011
Tags: @product
2:50.290
Before features/support/hooks.rb:269 0.008
Given a computer 0.272
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.028
Then Tails is running from USB drive "old" 0.404
And all tps features are active 1.977
When I write some files expected to persist 1.692
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.265
And all persistence configuration files have safe access rights 0.513
And all persistent directories from the old Tails version have safe access rights 2.578
And I take note of which tps features are available 0.452
And I shutdown Tails and wait for the computer to power off 4.393
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.711
After features/support/hooks.rb:315 0.114
After features/support/hooks.rb:100 0.011
Tags: @product
2:31.692
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 12.402
And I log in to a new session 18.578
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.688
And I plug USB drive "to_upgrade" 2.452
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.139
Then the running Tails is installed on USB drive "to_upgrade" 20.970
And I unplug USB drive "to_upgrade" 0.237
And I unplug USB drive "__internal" 0.223
After features/support/hooks.rb:315 2.133
After features/support/hooks.rb:100 0.000
Tags: @product
2:23.329
Before features/support/hooks.rb:269 0.008
Given a computer 0.261
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.381
Then all tps features from the old Tails version are active 1.761
And Tails is running from USB drive "to_upgrade" 0.388
And the boot device has safe access rights 3.322
And the expected persistent files created with the old Tails version are present in the filesystem 1.706
And all persistent directories from the old Tails version have safe access rights 2.507
After features/support/hooks.rb:315 0.926
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
7:10.079
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 25.430
And no SquashFS delta is installed 0.082
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.283
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.304
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.502
When the network is plugged 0.043
And Tor is ready 46.760
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.688
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.338
Given I shutdown Tails and wait for the computer to power off 11.146
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.914
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.369
And the file system changes introduced in version 6.2~testoverlayfs are present 0.285
And only the 6.2~testoverlayfs SquashFS delta is installed 0.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.380
# 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.314
When the network is plugged 0.041
And Tor is ready 22.559
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.960
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.407
Given I shutdown Tails and wait for the computer to power off 4.405
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.539
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.035
And the file system changes introduced in version 6.3~testoverlayfs are present 0.497
And only the 6.3~testoverlayfs SquashFS delta is installed 0.081
# 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.340
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.288
When the network is plugged 0.046
And Tor is ready 19.264
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 15.174
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.129
After features/support/hooks.rb:315 0.781
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
37.330
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.880
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.490
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 1.143
But a current signing key is available on our website 0.000
When the network is plugged 0.046
And Tor is ready 20.342
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.361
After features/support/hooks.rb:315 1.075
After features/support/hooks.rb:100 0.000