Project Number Date
test_Tails_ISO_stable 4868 03 Jun 2024, 18:15

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:39.796 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:9.714
Before features/support/hooks.rb:265 0.006
Given a computer 0.232
And I create a 7200 MiB disk named "old" 0.039
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 33.594
When I start Tails from USB drive "old" with network unplugged 1:30.728
Then the boot device has safe access rights 2.929
And Tails is running from USB drive "old" 0.359
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.107
And udev-watchdog is monitoring the correct device 0.342
And I unplug USB drive "old" 0.261
After features/support/hooks.rb:311 7.859
After features/support/hooks.rb:100 0.009
Tags: @product
2:11.149
Before features/support/hooks.rb:265 0.005
Given a computer 0.213
And I start Tails from USB drive "old" with network unplugged and I login 1:23.979
Then Tails is running from USB drive "old" 0.340
And I create a persistent partition 35.901
And I take note of which tps features are available 1.462
Then a Tails persistence partition exists on USB drive "old" 0.844
And I shutdown Tails and wait for the computer to power off 8.405
After features/support/hooks.rb:311 0.173
After features/support/hooks.rb:100 0.010
Tags: @product
3:5.441
Before features/support/hooks.rb:265 0.006
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:28.566
Then Tails is running from USB drive "old" 0.374
And all tps features are active 1.979
When I write some files expected to persist 1.857
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.223
And all persistence configuration files have safe access rights 0.372
And all persistent directories from the old Tails version have safe access rights 2.922
And I take note of which tps features are available 0.470
And I shutdown Tails and wait for the computer to power off 4.466
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.009
After features/support/hooks.rb:311 0.158
After features/support/hooks.rb:100 0.010
Tags: @product
2:22.939
Before features/support/hooks.rb:265 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 10.780
And I log in to a new session 18.083
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.327
And I plug USB drive "to_upgrade" 2.403
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.973
Then the running Tails is installed on USB drive "to_upgrade" 15.947
And I unplug USB drive "to_upgrade" 0.195
And I unplug USB drive "__internal" 0.227
After features/support/hooks.rb:311 3.078
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.079
Before features/support/hooks.rb:265 0.009
Given a computer 0.210
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.331
Then all tps features from the old Tails version are active 1.750
And Tails is running from USB drive "to_upgrade" 0.289
And the boot device has safe access rights 3.434
And the expected persistent files created with the old Tails version are present in the filesystem 1.656
And all persistent directories from the old Tails version have safe access rights 2.407
After features/support/hooks.rb:311 0.769
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
7:3.906
Before features/support/hooks.rb:265 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.414
And no SquashFS delta is installed 0.118
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.363
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.302
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.423
When the network is plugged 0.030
And Tor is ready 17.437
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.225
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.694
Given I shutdown Tails and wait for the computer to power off 8.880
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.273
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.622
And the file system changes introduced in version 6.2~testoverlayfs are present 0.297
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.345
# 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.263
When the network is plugged 0.029
And Tor is ready 44.469
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.585
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.337
Given I shutdown Tails and wait for the computer to power off 4.342
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.211
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.082
And the file system changes introduced in version 6.3~testoverlayfs are present 0.466
And only the 6.3~testoverlayfs SquashFS delta is installed 0.085
# 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.472
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.295
When the network is plugged 0.036
And Tor is ready 19.078
Then the Upgrader considers the system as up-to-date 10.750
# 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.975
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.822
After features/support/hooks.rb:311 0.702
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
34.565
Before features/support/hooks.rb:265 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.973
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.356
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 1.033
But a current signing key is available on our website 0.000
When the network is plugged 0.033
And Tor is ready 16.633
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.481
After features/support/hooks.rb:311 1.148
After features/support/hooks.rb:100 0.000