Project Number Date
test_Tails_ISO_stable 5262 13 Nov 2024, 12:39

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:31.818 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:14.434
Before features/support/hooks.rb:269 0.006
Given a computer 0.234
And I create a 7200 MiB disk named "old" 0.060
And I plug USB drive "old" 1.069
And I write an old version of the Tails USB image to disk "old" 31.453
When I start Tails from USB drive "old" with network unplugged 1:37.349
Then the boot device has safe access rights 3.182
And Tails is running from USB drive "old" 0.361
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.149
And udev-watchdog is monitoring the correct device 0.320
And I unplug USB drive "old" 0.173
After features/support/hooks.rb:326 3.507
After features/support/hooks.rb:100 0.030
Tags: @product
2:10.205
Before features/support/hooks.rb:269 0.005
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login 1:23.289
Then Tails is running from USB drive "old" 0.345
And I create a persistent partition 35.487
And I take note of which tps features are available 1.700
Then a Tails persistence partition exists on USB drive "old" 0.785
And I shutdown Tails and wait for the computer to power off 8.407
After features/support/hooks.rb:326 0.177
After features/support/hooks.rb:100 0.007
Tags: @product
2:58.313
Before features/support/hooks.rb:269 0.004
Given a computer 0.234
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.822
Then Tails is running from USB drive "old" 0.322
And all tps features are active 2.811
When I write some files expected to persist 2.098
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.278
And all persistence configuration files have safe access rights 0.400
And all persistent directories from the old Tails version have safe access rights 2.536
And I take note of which tps features are available 0.462
And I shutdown Tails and wait for the computer to power off 4.350
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.993
After features/support/hooks.rb:326 0.166
After features/support/hooks.rb:100 0.009
Tags: @product
2:29.689
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 10.931
And I log in to a new session 19.749
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.683
And I plug USB drive "to_upgrade" 2.463
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.247
Then the running Tails is installed on USB drive "to_upgrade" 19.210
And I unplug USB drive "to_upgrade" 0.195
And I unplug USB drive "__internal" 0.208
After features/support/hooks.rb:326 7.049
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.940
Before features/support/hooks.rb:269 0.005
Given a computer 0.198
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.511
Then all tps features from the old Tails version are active 1.645
And Tails is running from USB drive "to_upgrade" 0.368
And the boot device has safe access rights 3.401
And the expected persistent files created with the old Tails version are present in the filesystem 1.407
And all persistent directories from the old Tails version have safe access rights 2.408
After features/support/hooks.rb:326 1.082
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:43.754
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.694
And no SquashFS delta is installed 0.110
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.517
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.111
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.316
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.466
When the network is plugged 0.127
And Tor is ready 20.973
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.133
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.549
Given I shutdown Tails and wait for the computer to power off 1:23.537
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.787
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.190
And the file system changes introduced in version 6.2~testoverlayfs are present 0.311
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.342
# 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.288
When the network is plugged 0.083
And Tor is ready 18.045
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.183
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.026
Given I shutdown Tails and wait for the computer to power off 4.375
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.703
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.440
And the file system changes introduced in version 6.3~testoverlayfs are present 0.510
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.419
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.327
When the network is plugged 0.079
And Tor is ready 19.458
Then the Upgrader considers the system as up-to-date 0.310
# 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 15.092
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.057
After features/support/hooks.rb:326 0.787
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
36.480
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 9.891
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.420
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.087
And the signing key used by the Upgrader is outdated 0.965
But a current signing key is available on our website 0.000
When the network is plugged 0.073
And Tor is ready 18.488
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.553
After features/support/hooks.rb:326 0.708
After features/support/hooks.rb:100 0.000