Project Number Date
test_Tails_ISO_devel 3292 21 Feb 2024, 12:42

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 21:25.451 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
1:40.702
Before features/support/hooks.rb:245 0.004
Given a computer 0.181
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 20.268
When I start Tails from USB drive "old" with network unplugged 1:15.240
Then the boot device has safe access rights 2.928
And Tails is running from USB drive "old" 0.310
And there is no persistence partition on USB drive "old" 0.057
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.344
And I unplug USB drive "old" 0.177
After features/support/hooks.rb:291 7.180
After features/support/hooks.rb:75 0.008
Tags: @product
2:14.228
Before features/support/hooks.rb:245 0.005
Given a computer 0.178
And I start Tails from USB drive "old" with network unplugged and I login 1:22.351
Then Tails is running from USB drive "old" 0.405
And I create a persistent partition 41.554
And I take note of which tps features are available 1.801
Then a Tails persistence partition exists on USB drive "old" 0.749
And I shutdown Tails and wait for the computer to power off 7.187
After features/support/hooks.rb:291 0.156
After features/support/hooks.rb:75 0.010
Tags: @product
3:32.847
Before features/support/hooks.rb:245 0.006
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:3.328
Then Tails is running from USB drive "old" 0.345
And all tps features are active 2.154
When I write some files expected to persist 1.973
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.224
And all persistence configuration files have safe access rights 0.431
And all persistent directories from the old Tails version have safe access rights 2.767
And I take note of which tps features are available 0.446
And I shutdown Tails and wait for the computer to power off 4.065
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.925
After features/support/hooks.rb:291 0.171
After features/support/hooks.rb:75 0.015
Tags: @product
2:33.008
Before features/support/hooks.rb:245 0.012
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.787
And I log in to a new session 17.076
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.604
And I plug USB drive "to_upgrade" 2.504
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:47.286
Then the running Tails is installed on USB drive "to_upgrade" 13.374
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.171
After features/support/hooks.rb:291 3.576
After features/support/hooks.rb:75 0.000
Tags: @product
2:56.980
Before features/support/hooks.rb:245 0.006
Given a computer 0.199
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:46.765
Then all tps features from the old Tails version are active 1.568
And Tails is running from USB drive "to_upgrade" 0.458
And the boot device has safe access rights 3.605
And the expected persistent files created with the old Tails version are present in the filesystem 1.676
And all persistent directories from the old Tails version have safe access rights 2.705
After features/support/hooks.rb:291 0.916
After features/support/hooks.rb:75 0.013
Tags: @product @automatic_upgrade
7:49.751
Before features/support/hooks.rb:245 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.244
And no SquashFS delta is installed 0.065
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.265
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.305
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.423
When the network is plugged 0.070
And Tor is ready 21.490
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.962
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.919
Given I shutdown Tails and wait for the computer to power off 10.529
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:44.349
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.142
And the file system changes introduced in version 6.2~testoverlayfs are present 0.321
And only the 6.2~testoverlayfs SquashFS delta is installed 0.088
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.330
# 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.309
When the network is plugged 0.038
And Tor is ready 18.177
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.651
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.763
Given I shutdown Tails and wait for the computer to power off 5.572
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:41.849
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.489
And the file system changes introduced in version 6.3~testoverlayfs are present 0.603
And only the 6.3~testoverlayfs SquashFS delta is installed 0.078
# 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.291
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.266
When the network is plugged 0.057
And Tor is ready 19.057
Then the Upgrader considers the system as up-to-date 0.274
# 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 13.736
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.921
After features/support/hooks.rb:291 0.875
After features/support/hooks.rb:75 0.018
Tags: @product @automatic_upgrade
37.932
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.078
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.297
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.514
But a current signing key is available on our website 0.000
When the network is plugged 0.036
And Tor is ready 19.808
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.135
After features/support/hooks.rb:291 0.685
After features/support/hooks.rb:75 0.000