Project Number Date
test_Tails_ISO_devel 3549 15 Oct 2024, 19:22

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 22:12.580 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:52.690
Before features/support/hooks.rb:269 0.005
Given a computer 0.255
And I create a 7200 MiB disk named "old" 0.078
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 1:3.270
When I start Tails from USB drive "old" with network unplugged 1:43.544
Then the boot device has safe access rights 3.351
And Tails is running from USB drive "old" 0.367
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.131
And udev-watchdog is monitoring the correct device 0.337
And I unplug USB drive "old" 0.218
After features/support/hooks.rb:326 7.264
After features/support/hooks.rb:100 0.011
Tags: @product
2:10.954
Before features/support/hooks.rb:269 0.005
Given a computer 1.199
And I start Tails from USB drive "old" with network unplugged and I login 1:25.285
Then Tails is running from USB drive "old" 0.355
And I create a persistent partition 32.347
And I take note of which tps features are available 2.055
Then a Tails persistence partition exists on USB drive "old" 1.043
And I shutdown Tails and wait for the computer to power off 8.667
After features/support/hooks.rb:326 0.186
After features/support/hooks.rb:100 0.009
Tags: @product
3:12.655
Before features/support/hooks.rb:269 0.006
Given a computer 0.267
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:29.403
Then Tails is running from USB drive "old" 0.382
And all tps features are active 4.403
When I write some files expected to persist 1.933
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.291
And all persistence configuration files have safe access rights 0.470
And all persistent directories from the old Tails version have safe access rights 2.883
And I take note of which tps features are available 0.660
And I shutdown Tails and wait for the computer to power off 4.630
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 27.328
After features/support/hooks.rb:326 0.175
After features/support/hooks.rb:100 0.013
Tags: @product
2:56.809
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 26.974
And I log in to a new session 20.885
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.762
And I plug USB drive "to_upgrade" 2.526
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:45.323
Then the running Tails is installed on USB drive "to_upgrade" 18.889
And I unplug USB drive "to_upgrade" 0.215
And I unplug USB drive "__internal" 0.232
After features/support/hooks.rb:326 7.693
After features/support/hooks.rb:100 0.000
Tags: @product
2:32.077
Before features/support/hooks.rb:269 0.006
Given a computer 0.244
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:18.030
Then all tps features from the old Tails version are active 6.025
And Tails is running from USB drive "to_upgrade" 0.355
And the boot device has safe access rights 3.382
And the expected persistent files created with the old Tails version are present in the filesystem 1.377
And all persistent directories from the old Tails version have safe access rights 2.660
After features/support/hooks.rb:326 1.111
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:43.818
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 20.015
And no SquashFS delta is installed 0.128
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.946
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.100
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.363
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.487
When the network is plugged 0.108
And Tor is ready 24.039
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.377
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.381
Given I shutdown Tails and wait for the computer to power off 9.253
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:17.996
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.648
And the file system changes introduced in version 6.2~testoverlayfs are present 0.329
And only the 6.2~testoverlayfs SquashFS delta is installed 0.093
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.348
# 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.297
When the network is plugged 0.306
And Tor is ready 19.829
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.661
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.503
Given I shutdown Tails and wait for the computer to power off 4.755
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:44.956
Then Tails is running version 6.3~testoverlayfs 0.021
And all tps features are active 5.295
And the file system changes introduced in version 6.3~testoverlayfs are present 0.593
And only the 6.3~testoverlayfs SquashFS delta is installed 0.107
# 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.472
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.398
When the network is plugged 0.112
And Tor is ready 18.496
Then the Upgrader considers the system as up-to-date 0.361
# 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.905
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.110
After features/support/hooks.rb:326 0.763
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
43.575
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 11.694
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.552
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the signing key used by the Upgrader is outdated 0.979
But a current signing key is available on our website 0.000
When the network is plugged 0.078
And Tor is ready 22.861
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.332
After features/support/hooks.rb:326 0.757
After features/support/hooks.rb:100 0.000