Project Number Date
test_Tails_ISO_stable 5124 28 Sep 2024, 12:17

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:10.901 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:12.902
Before features/support/hooks.rb:269 0.004
Given a computer 0.190
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 29.271
When I start Tails from USB drive "old" with network unplugged 1:38.334
Then the boot device has safe access rights 3.023
And Tails is running from USB drive "old" 0.312
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.333
And I unplug USB drive "old" 0.175
After features/support/hooks.rb:326 3.509
After features/support/hooks.rb:100 0.008
Tags: @product
2:2.811
Before features/support/hooks.rb:269 0.003
Given a computer 0.178
And I start Tails from USB drive "old" with network unplugged and I login 1:21.323
Then Tails is running from USB drive "old" 0.302
And I create a persistent partition 30.443
And I take note of which tps features are available 1.580
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.199
After features/support/hooks.rb:326 0.229
After features/support/hooks.rb:100 0.009
Tags: @product
2:47.719
Before features/support/hooks.rb:269 0.005
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.288
Then Tails is running from USB drive "old" 0.358
And all tps features are active 1.964
When I write some files expected to persist 1.620
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.218
And all persistence configuration files have safe access rights 0.360
And all persistent directories from the old Tails version have safe access rights 2.448
And I take note of which tps features are available 0.507
And I shutdown Tails and wait for the computer to power off 4.618
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.136
After features/support/hooks.rb:326 0.166
After features/support/hooks.rb:100 0.008
Tags: @product
2:26.892
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.875
And I log in to a new session 20.944
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.540
And I plug USB drive "to_upgrade" 2.388
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.524
Then the running Tails is installed on USB drive "to_upgrade" 17.199
And I unplug USB drive "to_upgrade" 0.215
And I unplug USB drive "__internal" 0.203
After features/support/hooks.rb:326 3.541
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.108
Before features/support/hooks.rb:269 0.004
Given a computer 0.195
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.161
Then all tps features from the old Tails version are active 1.741
And Tails is running from USB drive "to_upgrade" 0.325
And the boot device has safe access rights 3.001
And the expected persistent files created with the old Tails version are present in the filesystem 1.363
And all persistent directories from the old Tails version have safe access rights 2.319
After features/support/hooks.rb:326 0.914
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:28.184
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 10.927
And no SquashFS delta is installed 0.101
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.384
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.265
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.409
When the network is plugged 0.075
And Tor is ready 18.339
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.528
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.043
Given I shutdown Tails and wait for the computer to power off 8.375
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.784
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.205
And the file system changes introduced in version 6.2~testoverlayfs are present 0.304
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.296
# 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.255
When the network is plugged 0.067
And Tor is ready 19.599
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.310
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.961
Given I shutdown Tails and wait for the computer to power off 4.303
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.679
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.002
And the file system changes introduced in version 6.3~testoverlayfs are present 0.521
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.309
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.265
When the network is plugged 0.070
And Tor is ready 17.508
Then the Upgrader considers the system as up-to-date 10.861
# 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.257
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.936
After features/support/hooks.rb:326 0.691
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
58.282
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.057
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.049
And the signing key used by the Upgrader is outdated 0.740
But a current signing key is available on our website 0.000
When the network is plugged 0.091
And Tor is ready 46.423
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.559
After features/support/hooks.rb:326 0.657
After features/support/hooks.rb:100 0.000