Project Number Date
test_Tails_ISO_stable 5084 09 Sep 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 19:3.532 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:13.738
Before features/support/hooks.rb:269 0.005
Given a computer 0.165
And I create a 7200 MiB disk named "old" 0.037
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 32.448
When I start Tails from USB drive "old" with network unplugged 1:34.579
Then the boot device has safe access rights 4.328
And Tails is running from USB drive "old" 0.345
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.112
And udev-watchdog is monitoring the correct device 0.365
And I unplug USB drive "old" 0.233
After features/support/hooks.rb:326 3.777
After features/support/hooks.rb:100 0.010
Tags: @product
2:7.075
Before features/support/hooks.rb:269 0.008
Given a computer 0.271
And I start Tails from USB drive "old" with network unplugged and I login 1:25.818
Then Tails is running from USB drive "old" 0.362
And I create a persistent partition 31.640
And I take note of which tps features are available 1.660
Then a Tails persistence partition exists on USB drive "old" 0.861
And I shutdown Tails and wait for the computer to power off 6.459
After features/support/hooks.rb:326 0.210
After features/support/hooks.rb:100 0.008
Tags: @product
3:1.864
Before features/support/hooks.rb:269 0.005
Given a computer 0.171
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.988
Then Tails is running from USB drive "old" 0.337
And all tps features are active 2.435
When I write some files expected to persist 1.730
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.239
And all persistence configuration files have safe access rights 0.430
And all persistent directories from the old Tails version have safe access rights 2.665
And I take note of which tps features are available 0.466
And I shutdown Tails and wait for the computer to power off 4.708
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.688
After features/support/hooks.rb:326 0.139
After features/support/hooks.rb:100 0.007
Tags: @product
2:31.026
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.355
And I log in to a new session 19.129
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.097
And I plug USB drive "to_upgrade" 2.386
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.494
Then the running Tails is installed on USB drive "to_upgrade" 21.147
And I unplug USB drive "to_upgrade" 0.209
And I unplug USB drive "__internal" 0.205
After features/support/hooks.rb:326 2.745
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.761
Before features/support/hooks.rb:269 0.006
Given a computer 0.599
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.399
Then all tps features from the old Tails version are active 1.696
And Tails is running from USB drive "to_upgrade" 0.325
And the boot device has safe access rights 3.549
And the expected persistent files created with the old Tails version are present in the filesystem 1.513
And all persistent directories from the old Tails version have safe access rights 2.678
After features/support/hooks.rb:326 0.661
After features/support/hooks.rb:100 0.053
Tags: @product @automatic_upgrade
6:19.122
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.407
And no SquashFS delta is installed 0.097
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.360
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.356
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.570
When the network is plugged 0.070
And Tor is ready 21.969
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.604
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.632
Given I shutdown Tails and wait for the computer to power off 8.733
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.980
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.262
And the file system changes introduced in version 6.2~testoverlayfs are present 0.310
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.394
# 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.340
When the network is plugged 0.070
And Tor is ready 19.586
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.167
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.673
Given I shutdown Tails and wait for the computer to power off 4.288
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.716
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.002
And the file system changes introduced in version 6.3~testoverlayfs are present 0.538
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.337
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.321
When the network is plugged 0.114
And Tor is ready 19.525
Then the Upgrader considers the system as up-to-date 0.334
# 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.015
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.100
After features/support/hooks.rb:326 0.726
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
36.943
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 10.345
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.419
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 0.748
But a current signing key is available on our website 0.000
When the network is plugged 0.063
And Tor is ready 18.494
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.809
After features/support/hooks.rb:326 0.699
After features/support/hooks.rb:100 0.000