Project Number Date
test_Tails_ISO_stable 4896 17 Jun 2024, 21:21

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:1.883 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:56.095
Before features/support/hooks.rb:269 0.008
Given a computer 0.210
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 29.040
When I start Tails from USB drive "old" with network unplugged 1:21.608
Then the boot device has safe access rights 3.123
And Tails is running from USB drive "old" 0.347
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.101
And udev-watchdog is monitoring the correct device 0.303
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:320 7.951
After features/support/hooks.rb:100 0.010
Tags: @product
2:7.393
Before features/support/hooks.rb:269 0.006
Given a computer 0.220
And I start Tails from USB drive "old" with network unplugged and I login 1:19.538
Then Tails is running from USB drive "old" 0.306
And I create a persistent partition 36.730
And I take note of which tps features are available 1.406
Then a Tails persistence partition exists on USB drive "old" 0.788
And I shutdown Tails and wait for the computer to power off 8.403
After features/support/hooks.rb:320 0.164
After features/support/hooks.rb:100 0.008
Tags: @product
2:40.365
Before features/support/hooks.rb:269 0.006
Given a computer 0.212
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:4.271
Then Tails is running from USB drive "old" 0.375
And all tps features are active 1.995
When I write some files expected to persist 1.681
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.207
And all persistence configuration files have safe access rights 0.371
And all persistent directories from the old Tails version have safe access rights 2.376
And I take note of which tps features are available 0.461
And I shutdown Tails and wait for the computer to power off 4.151
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.259
After features/support/hooks.rb:320 0.093
After features/support/hooks.rb:100 0.010
Tags: @product
2:28.667
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 10.914
And I log in to a new session 18.147
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.406
And I plug USB drive "to_upgrade" 2.398
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.070
Then the running Tails is installed on USB drive "to_upgrade" 15.339
And I unplug USB drive "to_upgrade" 0.191
And I unplug USB drive "__internal" 0.197
After features/support/hooks.rb:320 2.902
After features/support/hooks.rb:100 0.000
Tags: @product
2:3.805
Before features/support/hooks.rb:269 0.007
Given a computer 0.208
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:55.070
Then all tps features from the old Tails version are active 1.525
And Tails is running from USB drive "to_upgrade" 0.320
And the boot device has safe access rights 2.906
And the expected persistent files created with the old Tails version are present in the filesystem 1.588
And all persistent directories from the old Tails version have safe access rights 2.185
After features/support/hooks.rb:320 0.884
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:7.913
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.913
And no SquashFS delta is installed 0.209
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.278
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.285
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.397
When the network is plugged 0.144
And Tor is ready 22.457
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.278
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.959
Given I shutdown Tails and wait for the computer to power off 1:11.933
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.188
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 1.956
And the file system changes introduced in version 6.2~testoverlayfs are present 0.257
And only the 6.2~testoverlayfs SquashFS delta is installed 0.056
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.325
# 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.237
When the network is plugged 0.045
And Tor is ready 16.570
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.488
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.994
Given I shutdown Tails and wait for the computer to power off 4.449
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.982
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.987
And the file system changes introduced in version 6.3~testoverlayfs are present 0.604
And only the 6.3~testoverlayfs SquashFS delta is installed 0.078
# 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.376
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.336
When the network is plugged 0.045
And Tor is ready 19.923
Then the Upgrader considers the system as up-to-date 0.324
# 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.806
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.926
After features/support/hooks.rb:320 0.738
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
37.642
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 9.384
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.351
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 1.241
But a current signing key is available on our website 0.000
When the network is plugged 0.033
And Tor is ready 21.647
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.909
After features/support/hooks.rb:320 0.647
After features/support/hooks.rb:100 0.000