Project Number Date
test_Tails_ISO_stable 5218 24 Oct 2024, 16: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 18:52.904 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:3.562
Before features/support/hooks.rb:269 0.005
Given a computer 0.201
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 29.599
When I start Tails from USB drive "old" with network unplugged 1:28.495
Then the boot device has safe access rights 3.144
And Tails is running from USB drive "old" 0.338
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.336
And I unplug USB drive "old" 0.183
After features/support/hooks.rb:326 4.151
After features/support/hooks.rb:100 0.009
Tags: @product
2:4.228
Before features/support/hooks.rb:269 0.006
Given a computer 0.217
And I start Tails from USB drive "old" with network unplugged and I login 1:20.270
Then Tails is running from USB drive "old" 0.337
And I create a persistent partition 32.412
And I take note of which tps features are available 1.800
Then a Tails persistence partition exists on USB drive "old" 0.927
And I shutdown Tails and wait for the computer to power off 8.262
After features/support/hooks.rb:326 0.152
After features/support/hooks.rb:100 0.007
Tags: @product
2:46.290
Before features/support/hooks.rb:269 0.003
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:9.554
Then Tails is running from USB drive "old" 0.734
And all tps features are active 2.029
When I write some files expected to persist 1.690
# 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.523
And all persistent directories from the old Tails version have safe access rights 2.675
And I take note of which tps features are available 0.428
And I shutdown Tails and wait for the computer to power off 4.295
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.865
After features/support/hooks.rb:326 0.109
After features/support/hooks.rb:100 0.009
Tags: @product
2:37.469
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.729
And I log in to a new session 18.961
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.571
And I plug USB drive "to_upgrade" 2.432
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:43.052
Then the running Tails is installed on USB drive "to_upgrade" 20.311
And I unplug USB drive "to_upgrade" 0.213
And I unplug USB drive "__internal" 0.197
After features/support/hooks.rb:326 2.344
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.178
Before features/support/hooks.rb:269 0.005
Given a computer 0.178
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.543
Then all tps features from the old Tails version are active 1.663
And Tails is running from USB drive "to_upgrade" 0.382
And the boot device has safe access rights 3.279
And the expected persistent files created with the old Tails version are present in the filesystem 1.646
And all persistent directories from the old Tails version have safe access rights 2.485
After features/support/hooks.rb:326 0.768
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:31.158
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 33.412
And no SquashFS delta is installed 0.174
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.724
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.271
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.414
When the network is plugged 0.142
And Tor is ready 21.131
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.484
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.166
Given I shutdown Tails and wait for the computer to power off 8.427
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.383
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.060
And the file system changes introduced in version 6.2~testoverlayfs are present 0.280
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.398
# 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.399
When the network is plugged 0.069
And Tor is ready 18.862
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.985
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.397
Given I shutdown Tails and wait for the computer to power off 4.271
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.106
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.126
And the file system changes introduced in version 6.3~testoverlayfs are present 0.470
And only the 6.3~testoverlayfs SquashFS delta is installed 0.086
# 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.360
When the network is plugged 0.084
And Tor is ready 18.665
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 14.073
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.909
After features/support/hooks.rb:326 0.748
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
37.017
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 9.270
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.307
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.722
But a current signing key is available on our website 0.000
When the network is plugged 0.062
And Tor is ready 20.414
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.179
After features/support/hooks.rb:326 0.685
After features/support/hooks.rb:100 0.000