Project Number Date
test_Tails_ISO_devel 3504 05 Sep 2024, 12:51

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:15.838 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:7.463
Before features/support/hooks.rb:269 0.006
Given a computer 0.248
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 30.259
When I start Tails from USB drive "old" with network unplugged 1:31.550
Then the boot device has safe access rights 3.211
And Tails is running from USB drive "old" 0.413
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.332
And I unplug USB drive "old" 0.182
After features/support/hooks.rb:326 3.539
After features/support/hooks.rb:100 0.008
Tags: @product
2:5.743
Before features/support/hooks.rb:269 0.005
Given a computer 0.201
And I start Tails from USB drive "old" with network unplugged and I login 1:23.458
Then Tails is running from USB drive "old" 0.345
And I create a persistent partition 30.099
And I take note of which tps features are available 1.938
Then a Tails persistence partition exists on USB drive "old" 0.893
And I shutdown Tails and wait for the computer to power off 8.806
After features/support/hooks.rb:326 0.221
After features/support/hooks.rb:100 0.009
Tags: @product
2:45.875
Before features/support/hooks.rb:269 0.006
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:9.096
Then Tails is running from USB drive "old" 0.363
And all tps features are active 2.055
When I write some files expected to persist 1.642
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.247
And all persistence configuration files have safe access rights 0.366
And all persistent directories from the old Tails version have safe access rights 2.558
And I take note of which tps features are available 0.469
And I shutdown Tails and wait for the computer to power off 4.374
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.514
After features/support/hooks.rb:326 0.130
After features/support/hooks.rb:100 0.009
Tags: @product
2:33.469
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 11.713
And I log in to a new session 20.199
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.647
And I plug USB drive "to_upgrade" 2.415
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.191
Then the running Tails is installed on USB drive "to_upgrade" 22.888
And I unplug USB drive "to_upgrade" 0.207
And I unplug USB drive "__internal" 0.206
After features/support/hooks.rb:326 2.860
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.036
Before features/support/hooks.rb:269 0.006
Given a computer 0.179
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.245
Then all tps features from the old Tails version are active 1.796
And Tails is running from USB drive "to_upgrade" 0.338
And the boot device has safe access rights 3.197
And the expected persistent files created with the old Tails version are present in the filesystem 1.789
And all persistent directories from the old Tails version have safe access rights 2.489
After features/support/hooks.rb:326 1.018
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:22.635
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.848
And no SquashFS delta is installed 0.083
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.302
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.101
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.299
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.446
When the network is plugged 0.081
And Tor is ready 18.863
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.380
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.293
Given I shutdown Tails and wait for the computer to power off 10.864
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.298
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.136
And the file system changes introduced in version 6.2~testoverlayfs are present 0.325
And only the 6.2~testoverlayfs SquashFS delta is installed 0.085
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.354
# 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.079
And Tor is ready 22.267
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.016
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.577
Given I shutdown Tails and wait for the computer to power off 4.350
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.983
Then Tails is running version 6.3~testoverlayfs 0.022
And all tps features are active 2.058
And the file system changes introduced in version 6.3~testoverlayfs are present 0.555
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.307
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.303
When the network is plugged 0.076
And Tor is ready 19.725
Then the Upgrader considers the system as up-to-date 0.320
# 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.840
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.035
After features/support/hooks.rb:326 0.730
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
58.613
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.284
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.061
And the signing key used by the Upgrader is outdated 0.969
But a current signing key is available on our website 0.000
When the network is plugged 0.228
And Tor is ready 46.196
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.564
After features/support/hooks.rb:326 0.660
After features/support/hooks.rb:100 0.000