Project Number Date
test_Tails_ISO_stable 5064 02 Sep 2024, 12:30

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 20:26.743 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:30.105
Before features/support/hooks.rb:269 0.005
Given a computer 0.596
And I create a 7200 MiB disk named "old" 0.259
And I plug USB drive "old" 1.214
And I write an old version of the Tails USB image to disk "old" 43.015
When I start Tails from USB drive "old" with network unplugged 1:39.804
Then the boot device has safe access rights 3.306
And Tails is running from USB drive "old" 0.340
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.088
And udev-watchdog is monitoring the correct device 0.616
And I unplug USB drive "old" 0.798
After features/support/hooks.rb:326 3.724
After features/support/hooks.rb:100 0.009
Tags: @product
2:10.306
Before features/support/hooks.rb:269 0.005
Given a computer 0.270
And I start Tails from USB drive "old" with network unplugged and I login 1:27.101
Then Tails is running from USB drive "old" 0.368
And I create a persistent partition 31.517
And I take note of which tps features are available 1.967
Then a Tails persistence partition exists on USB drive "old" 0.783
And I shutdown Tails and wait for the computer to power off 8.296
After features/support/hooks.rb:326 0.161
After features/support/hooks.rb:100 0.009
Tags: @product
3:9.679
Before features/support/hooks.rb:269 0.004
Given a computer 0.257
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:31.236
Then Tails is running from USB drive "old" 0.594
And all tps features are active 2.379
When I write some files expected to persist 1.977
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.311
And all persistence configuration files have safe access rights 0.506
And all persistent directories from the old Tails version have safe access rights 2.554
And I take note of which tps features are available 0.536
And I shutdown Tails and wait for the computer to power off 4.361
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.962
After features/support/hooks.rb:326 0.151
After features/support/hooks.rb:100 0.007
Tags: @product
2:40.468
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.340
And I log in to a new session 20.185
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.518
And I plug USB drive "to_upgrade" 3.092
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.882
Then the running Tails is installed on USB drive "to_upgrade" 23.020
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.224
After features/support/hooks.rb:326 2.365
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.790
Before features/support/hooks.rb:269 0.008
Given a computer 0.250
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.055
Then all tps features from the old Tails version are active 3.077
And Tails is running from USB drive "to_upgrade" 0.411
And the boot device has safe access rights 3.742
And the expected persistent files created with the old Tails version are present in the filesystem 1.589
And all persistent directories from the old Tails version have safe access rights 2.663
After features/support/hooks.rb:326 0.988
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:0.403
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 34.173
And no SquashFS delta is installed 0.092
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.347
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.298
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.508
When the network is plugged 0.095
And Tor is ready 20.000
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.090
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.417
Given I shutdown Tails and wait for the computer to power off 10.916
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.217
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.349
And the file system changes introduced in version 6.2~testoverlayfs are present 0.338
And only the 6.2~testoverlayfs SquashFS delta is installed 0.091
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.316
# 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.305
When the network is plugged 0.080
And Tor is ready 19.374
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.654
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.390
Given I shutdown Tails and wait for the computer to power off 6.756
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.488
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.288
And the file system changes introduced in version 6.3~testoverlayfs are present 0.493
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.320
When the network is plugged 0.081
And Tor is ready 18.393
Then the Upgrader considers the system as up-to-date 0.327
# 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.706
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.012
After features/support/hooks.rb:326 0.769
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
35.989
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 10.424
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.413
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.830
But a current signing key is available on our website 0.000
When the network is plugged 0.072
And Tor is ready 16.470
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.719
After features/support/hooks.rb:326 1.476
After features/support/hooks.rb:100 0.000