Project Number Date
test_Tails_ISO_devel 3438 25 Jun 2024, 12:48

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:5.522 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:48.735
Before features/support/hooks.rb:269 0.007
Given a computer 0.248
And I create a 7200 MiB disk named "old" 0.064
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 54.038
When I start Tails from USB drive "old" with network unplugged 1:49.472
Then the boot device has safe access rights 2.900
And Tails is running from USB drive "old" 0.305
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.079
And udev-watchdog is monitoring the correct device 0.320
And I unplug USB drive "old" 0.181
After features/support/hooks.rb:326 3.487
After features/support/hooks.rb:100 0.047
Tags: @product
2:2.258
Before features/support/hooks.rb:269 0.007
Given a computer 0.240
And I start Tails from USB drive "old" with network unplugged and I login 1:19.728
Then Tails is running from USB drive "old" 0.305
And I create a persistent partition 31.591
And I take note of which tps features are available 1.431
Then a Tails persistence partition exists on USB drive "old" 0.784
And I shutdown Tails and wait for the computer to power off 8.176
After features/support/hooks.rb:326 0.187
After features/support/hooks.rb:100 0.011
Tags: @product
2:57.588
Before features/support/hooks.rb:269 0.007
Given a computer 0.213
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.545
Then Tails is running from USB drive "old" 0.310
And all tps features are active 2.001
When I write some files expected to persist 1.781
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.221
And all persistence configuration files have safe access rights 0.441
And all persistent directories from the old Tails version have safe access rights 2.185
And I take note of which tps features are available 0.611
And I shutdown Tails and wait for the computer to power off 4.280
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.995
After features/support/hooks.rb:326 0.134
After features/support/hooks.rb:100 0.011
Tags: @product
2:23.094
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.485
And I log in to a new session 18.624
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.386
And I plug USB drive "to_upgrade" 2.435
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.553
Then the running Tails is installed on USB drive "to_upgrade" 17.192
And I unplug USB drive "to_upgrade" 0.208
And I unplug USB drive "__internal" 0.206
After features/support/hooks.rb:326 6.648
After features/support/hooks.rb:100 0.000
Tags: @product
2:9.823
Before features/support/hooks.rb:269 0.009
Given a computer 0.255
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:0.155
Then all tps features from the old Tails version are active 1.691
And Tails is running from USB drive "to_upgrade" 0.356
And the boot device has safe access rights 3.420
And the expected persistent files created with the old Tails version are present in the filesystem 1.492
And all persistent directories from the old Tails version have safe access rights 2.453
After features/support/hooks.rb:326 0.697
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
6:8.767
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.070
And no SquashFS delta is installed 0.123
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.476
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.321
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.401
When the network is plugged 0.044
And Tor is ready 21.104
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.405
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.600
Given I shutdown Tails and wait for the computer to power off 8.504
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.938
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.103
And the file system changes introduced in version 6.2~testoverlayfs are present 0.323
And only the 6.2~testoverlayfs SquashFS delta is installed 0.114
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.370
# 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.259
When the network is plugged 0.038
And Tor is ready 18.569
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.819
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.925
Given I shutdown Tails and wait for the computer to power off 4.321
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.853
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.039
And the file system changes introduced in version 6.3~testoverlayfs are present 0.456
And only the 6.3~testoverlayfs SquashFS delta is installed 0.081
# 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.310
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.314
When the network is plugged 0.049
And Tor is ready 16.923
Then the Upgrader considers the system as up-to-date 0.319
# 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.464
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.022
After features/support/hooks.rb:326 0.707
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
35.254
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.482
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.256
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.949
But a current signing key is available on our website 0.000
When the network is plugged 0.037
And Tor is ready 19.262
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.212
After features/support/hooks.rb:326 0.675
After features/support/hooks.rb:100 0.000