Project Number Date
test_Tails_ISO_devel 3507 08 Sep 2024, 12:29

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:24.374 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
1:55.309
Before features/support/hooks.rb:269 0.005
Given a computer 0.175
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 30.052
When I start Tails from USB drive "old" with network unplugged 1:20.167
Then the boot device has safe access rights 2.869
And Tails is running from USB drive "old" 0.302
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.289
And I unplug USB drive "old" 0.194
After features/support/hooks.rb:326 6.992
After features/support/hooks.rb:100 0.009
Tags: @product
2:3.973
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:19.754
Then Tails is running from USB drive "old" 0.314
And I create a persistent partition 32.745
And I take note of which tps features are available 1.511
Then a Tails persistence partition exists on USB drive "old" 0.810
And I shutdown Tails and wait for the computer to power off 8.632
After features/support/hooks.rb:326 0.168
After features/support/hooks.rb:100 0.012
Tags: @product
2:47.898
Before features/support/hooks.rb:269 0.005
Given a computer 0.212
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.677
Then Tails is running from USB drive "old" 0.308
And all tps features are active 1.959
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.234
And all persistence configuration files have safe access rights 0.395
And all persistent directories from the old Tails version have safe access rights 2.634
And I take note of which tps features are available 0.468
And I shutdown Tails and wait for the computer to power off 4.196
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.117
After features/support/hooks.rb:326 0.099
After features/support/hooks.rb:100 0.009
Tags: @product
2:28.182
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 11.029
And I log in to a new session 18.708
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.585
And I plug USB drive "to_upgrade" 2.412
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.937
Then the running Tails is installed on USB drive "to_upgrade" 19.101
And I unplug USB drive "to_upgrade" 0.187
And I unplug USB drive "__internal" 0.220
After features/support/hooks.rb:326 2.578
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.827
Before features/support/hooks.rb:269 0.005
Given a computer 0.190
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.564
Then all tps features from the old Tails version are active 1.718
And Tails is running from USB drive "to_upgrade" 0.321
And the boot device has safe access rights 3.361
And the expected persistent files created with the old Tails version are present in the filesystem 1.324
And all persistent directories from the old Tails version have safe access rights 2.346
After features/support/hooks.rb:326 0.624
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:21.015
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.662
And no SquashFS delta is installed 0.077
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.311
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.293
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.501
When the network is plugged 0.298
And Tor is ready 21.090
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.872
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.440
Given I shutdown Tails and wait for the computer to power off 8.417
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.089
Then Tails is running version 6.2~testoverlayfs 0.037
And all tps features are active 2.161
And the file system changes introduced in version 6.2~testoverlayfs are present 0.439
And only the 6.2~testoverlayfs SquashFS delta is installed 0.086
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.531
# 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.264
When the network is plugged 0.089
And Tor is ready 16.857
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.074
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.615
Given I shutdown Tails and wait for the computer to power off 4.283
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.806
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.072
And the file system changes introduced in version 6.3~testoverlayfs are present 0.479
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.315
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.284
When the network is plugged 0.067
And Tor is ready 17.259
Then the Upgrader considers the system as up-to-date 10.874
# 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.277
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.935
After features/support/hooks.rb:326 0.772
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
33.167
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.601
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.309
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.083
And the signing key used by the Upgrader is outdated 1.012
But a current signing key is available on our website 0.000
When the network is plugged 0.062
And Tor is ready 16.061
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.035
After features/support/hooks.rb:326 1.471
After features/support/hooks.rb:100 0.000