Project Number Date
test_Tails_ISO_devel 3611 13 Dec 2024, 12:55

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:56.696 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:1.931
Before features/support/hooks.rb:269 0.006
Given a computer 0.222
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.076
And I write an old version of the Tails USB image to disk "old" 29.295
When I start Tails from USB drive "old" with network unplugged 1:27.127
Then the boot device has safe access rights 3.143
And Tails is running from USB drive "old" 0.340
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.106
And udev-watchdog is monitoring the correct device 0.316
And I unplug USB drive "old" 0.181
After features/support/hooks.rb:326 7.093
After features/support/hooks.rb:100 0.008
Tags: @product
2:6.529
Before features/support/hooks.rb:269 0.004
Given a computer 0.224
And I start Tails from USB drive "old" with network unplugged and I login 1:23.672
Then Tails is running from USB drive "old" 0.367
And I create a persistent partition 31.944
And I take note of which tps features are available 1.390
Then a Tails persistence partition exists on USB drive "old" 0.725
And I shutdown Tails and wait for the computer to power off 8.204
After features/support/hooks.rb:326 0.173
After features/support/hooks.rb:100 0.008
Tags: @product
3:2.091
Before features/support/hooks.rb:269 0.006
Given a computer 0.929
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:25.199
Then Tails is running from USB drive "old" 0.350
And all tps features are active 2.154
When I write some files expected to persist 1.675
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.211
And all persistence configuration files have safe access rights 0.381
And all persistent directories from the old Tails version have safe access rights 2.395
And I take note of which tps features are available 0.458
And I shutdown Tails and wait for the computer to power off 4.294
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.041
After features/support/hooks.rb:326 0.097
After features/support/hooks.rb:100 0.010
Tags: @product
2:39.163
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.208
And I log in to a new session 22.283
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.672
And I plug USB drive "to_upgrade" 2.412
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.165
Then the running Tails is installed on USB drive "to_upgrade" 23.923
And I unplug USB drive "to_upgrade" 0.265
And I unplug USB drive "__internal" 0.232
After features/support/hooks.rb:326 2.055
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.224
Before features/support/hooks.rb:269 0.005
Given a computer 0.347
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.751
Then all tps features from the old Tails version are active 1.731
And Tails is running from USB drive "to_upgrade" 0.368
And the boot device has safe access rights 3.301
And the expected persistent files created with the old Tails version are present in the filesystem 1.383
And all persistent directories from the old Tails version have safe access rights 2.341
After features/support/hooks.rb:326 0.608
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
6:12.022
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.865
And no SquashFS delta is installed 0.094
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.980
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.189
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.319
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.436
When the network is plugged 0.096
And Tor is ready 23.132
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.620
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.715
Given I shutdown Tails and wait for the computer to power off 8.834
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.473
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.216
And the file system changes introduced in version 6.2~testoverlayfs are present 0.279
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.302
# 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.275
When the network is plugged 0.077
And Tor is ready 19.047
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.534
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.216
Given I shutdown Tails and wait for the computer to power off 4.318
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.760
Then Tails is running version 6.3~testoverlayfs 0.021
And all tps features are active 1.981
And the file system changes introduced in version 6.3~testoverlayfs are present 0.546
And only the 6.3~testoverlayfs SquashFS delta is installed 0.088
# 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.342
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.304
When the network is plugged 0.066
And Tor is ready 18.243
Then the Upgrader considers the system as up-to-date 0.357
# 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 15.071
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.128
After features/support/hooks.rb:326 0.766
After features/support/hooks.rb:100 0.049
Tags: @product @automatic_upgrade
37.735
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 10.260
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.308
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the signing key used by the Upgrader is outdated 0.733
But a current signing key is available on our website 0.000
When the network is plugged 0.074
And Tor is ready 19.965
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.321
After features/support/hooks.rb:326 0.740
After features/support/hooks.rb:100 0.000