Project Number Date
test_Tails_ISO_stable 5186 16 Oct 2024, 12:41

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:23.393 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:18.227
Before features/support/hooks.rb:269 0.005
Given a computer 0.167
And I create a 7200 MiB disk named "old" 0.040
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 33.426
When I start Tails from USB drive "old" with network unplugged 1:39.744
Then the boot device has safe access rights 2.862
And Tails is running from USB drive "old" 0.307
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.292
And I unplug USB drive "old" 0.177
After features/support/hooks.rb:326 3.701
After features/support/hooks.rb:100 0.009
Tags: @product
2:18.379
Before features/support/hooks.rb:269 0.005
Given a computer 0.161
And I start Tails from USB drive "old" with network unplugged and I login 1:31.362
Then Tails is running from USB drive "old" 0.375
And I create a persistent partition 35.907
And I take note of which tps features are available 1.466
Then a Tails persistence partition exists on USB drive "old" 0.773
And I shutdown Tails and wait for the computer to power off 8.332
After features/support/hooks.rb:326 0.188
After features/support/hooks.rb:100 0.007
Tags: @product
2:51.036
Before features/support/hooks.rb:269 0.005
Given a computer 0.214
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.031
Then Tails is running from USB drive "old" 0.340
And all tps features are active 2.099
When I write some files expected to persist 1.598
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.222
And all persistence configuration files have safe access rights 0.366
And all persistent directories from the old Tails version have safe access rights 2.353
And I take note of which tps features are available 0.401
And I shutdown Tails and wait for the computer to power off 4.377
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.030
After features/support/hooks.rb:326 0.087
After features/support/hooks.rb:100 0.009
Tags: @product
2:30.083
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.168
And I log in to a new session 19.316
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.044
And I plug USB drive "to_upgrade" 2.419
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.583
Then the running Tails is installed on USB drive "to_upgrade" 18.131
And I unplug USB drive "to_upgrade" 0.191
And I unplug USB drive "__internal" 0.228
After features/support/hooks.rb:326 2.303
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.810
Before features/support/hooks.rb:269 0.006
Given a computer 0.187
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.651
Then all tps features from the old Tails version are active 1.657
And Tails is running from USB drive "to_upgrade" 0.324
And the boot device has safe access rights 3.372
And the expected persistent files created with the old Tails version are present in the filesystem 1.948
And all persistent directories from the old Tails version have safe access rights 2.667
After features/support/hooks.rb:326 1.020
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:36.952
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.499
And no SquashFS delta is installed 0.064
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.389
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.296
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.433
When the network is plugged 0.066
And Tor is ready 48.913
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.605
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.778
Given I shutdown Tails and wait for the computer to power off 8.530
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.456
Then Tails is running version 6.2~testoverlayfs 0.023
And all tps features are active 2.128
And the file system changes introduced in version 6.2~testoverlayfs are present 0.315
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.299
# 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.298
When the network is plugged 0.072
And Tor is ready 20.190
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.480
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.047
Given I shutdown Tails and wait for the computer to power off 4.263
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.133
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.112
And the file system changes introduced in version 6.3~testoverlayfs are present 0.498
And only the 6.3~testoverlayfs SquashFS delta is installed 0.083
# 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.318
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.271
When the network is plugged 0.071
And Tor is ready 18.175
Then the Upgrader considers the system as up-to-date 0.306
# 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 13.597
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.082
After features/support/hooks.rb:326 0.748
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
35.903
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.491
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.397
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.841
But a current signing key is available on our website 0.000
When the network is plugged 0.064
And Tor is ready 16.959
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.088
After features/support/hooks.rb:326 0.676
After features/support/hooks.rb:100 0.000