Project Number Date
test_Tails_ISO_devel 3484 18 Aug 2024, 12:36

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:4.140 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.630
Before features/support/hooks.rb:269 0.005
Given a computer 0.188
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 30.302
When I start Tails from USB drive "old" with network unplugged 1:32.319
Then the boot device has safe access rights 2.838
And Tails is running from USB drive "old" 0.285
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.084
And udev-watchdog is monitoring the correct device 0.276
And I unplug USB drive "old" 0.175
After features/support/hooks.rb:326 7.010
After features/support/hooks.rb:100 0.008
Tags: @product
2:9.312
Before features/support/hooks.rb:269 0.005
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login 1:26.834
Then Tails is running from USB drive "old" 0.325
And I create a persistent partition 31.471
And I take note of which tps features are available 1.445
Then a Tails persistence partition exists on USB drive "old" 0.730
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.008
Tags: @product
2:50.238
Before features/support/hooks.rb:269 0.007
Given a computer 0.179
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.919
Then Tails is running from USB drive "old" 0.369
And all tps features are active 2.211
When I write some files expected to persist 1.734
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.322
And all persistence configuration files have safe access rights 0.418
And all persistent directories from the old Tails version have safe access rights 2.742
And I take note of which tps features are available 0.496
And I shutdown Tails and wait for the computer to power off 4.082
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.761
After features/support/hooks.rb:326 0.149
After features/support/hooks.rb:100 0.014
Tags: @product
2:30.145
Before features/support/hooks.rb:269 0.010
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.588
And I log in to a new session 19.780
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.524
And I plug USB drive "to_upgrade" 2.406
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.581
Then the running Tails is installed on USB drive "to_upgrade" 20.864
And I unplug USB drive "to_upgrade" 0.192
And I unplug USB drive "__internal" 0.206
After features/support/hooks.rb:326 2.351
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.542
Before features/support/hooks.rb:269 0.006
Given a computer 0.199
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.169
Then all tps features from the old Tails version are active 1.596
And Tails is running from USB drive "to_upgrade" 0.298
And the boot device has safe access rights 3.200
And the expected persistent files created with the old Tails version are present in the filesystem 1.360
And all persistent directories from the old Tails version have safe access rights 2.717
After features/support/hooks.rb:326 0.826
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:28.016
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.972
And no SquashFS delta is installed 0.104
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.548
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.301
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.409
When the network is plugged 0.065
And Tor is ready 18.238
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.579
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.512
Given I shutdown Tails and wait for the computer to power off 10.756
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.756
Then Tails is running version 6.2~testoverlayfs 0.041
And all tps features are active 2.342
And the file system changes introduced in version 6.2~testoverlayfs are present 0.303
And only the 6.2~testoverlayfs SquashFS delta is installed 0.084
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.341
# 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.143
And Tor is ready 17.943
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.132
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.694
Given I shutdown Tails and wait for the computer to power off 4.339
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.442
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.056
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.069
# 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.298
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.286
When the network is plugged 0.065
And Tor is ready 18.923
Then the Upgrader considers the system as up-to-date 0.341
# 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.171
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.937
After features/support/hooks.rb:326 0.858
After features/support/hooks.rb:100 0.070
Tags: @product @automatic_upgrade
40.253
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 13.435
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.316
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 0.912
But a current signing key is available on our website 0.000
When the network is plugged 0.065
And Tor is ready 19.035
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.423
After features/support/hooks.rb:326 0.737
After features/support/hooks.rb:100 0.000