Project Number Date
test_Tails_ISO_devel 3485 19 Aug 2024, 12:26

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:47.023 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:3.728
Before features/support/hooks.rb:269 0.005
Given a computer 0.214
And I create a 7200 MiB disk named "old" 0.055
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 29.784
When I start Tails from USB drive "old" with network unplugged 1:28.577
Then the boot device has safe access rights 3.019
And Tails is running from USB drive "old" 0.359
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.089
And udev-watchdog is monitoring the correct device 0.312
And I unplug USB drive "old" 0.194
After features/support/hooks.rb:326 7.124
After features/support/hooks.rb:100 0.010
Tags: @product
2:9.762
Before features/support/hooks.rb:269 0.007
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login 1:25.730
Then Tails is running from USB drive "old" 0.328
And I create a persistent partition 32.965
And I take note of which tps features are available 1.416
Then a Tails persistence partition exists on USB drive "old" 0.796
And I shutdown Tails and wait for the computer to power off 8.335
After features/support/hooks.rb:326 0.177
After features/support/hooks.rb:100 0.010
Tags: @product
2:51.131
Before features/support/hooks.rb:269 0.007
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.811
Then Tails is running from USB drive "old" 0.311
And all tps features are active 2.082
When I write some files expected to persist 2.527
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.273
And all persistence configuration files have safe access rights 0.453
And all persistent directories from the old Tails version have safe access rights 2.490
And I take note of which tps features are available 0.527
And I shutdown Tails and wait for the computer to power off 4.488
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.980
After features/support/hooks.rb:326 0.134
After features/support/hooks.rb:100 0.014
Tags: @product
2:35.095
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.331
And I log in to a new session 24.357
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.423
And I plug USB drive "to_upgrade" 2.348
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.639
Then the running Tails is installed on USB drive "to_upgrade" 20.575
And I unplug USB drive "to_upgrade" 0.211
And I unplug USB drive "__internal" 0.207
After features/support/hooks.rb:326 2.129
After features/support/hooks.rb:100 0.000
Tags: @product
2:10.626
Before features/support/hooks.rb:269 0.007
Given a computer 0.198
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.235
Then all tps features from the old Tails version are active 1.705
And Tails is running from USB drive "to_upgrade" 0.301
And the boot device has safe access rights 3.419
And the expected persistent files created with the old Tails version are present in the filesystem 1.323
And all persistent directories from the old Tails version have safe access rights 2.442
After features/support/hooks.rb:326 0.733
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:20.624
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.794
And no SquashFS delta is installed 0.215
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.293
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.265
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.430
When the network is plugged 0.068
And Tor is ready 17.945
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.372
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.805
Given I shutdown Tails and wait for the computer to power off 1:13.350
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.599
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.244
And the file system changes introduced in version 6.2~testoverlayfs are present 0.298
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.427
# 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.311
When the network is plugged 0.081
And Tor is ready 19.165
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.073
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.293
Given I shutdown Tails and wait for the computer to power off 6.385
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.558
Then Tails is running version 6.3~testoverlayfs 0.064
And all tps features are active 2.039
And the file system changes introduced in version 6.3~testoverlayfs are present 0.461
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.354
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.274
When the network is plugged 0.089
And Tor is ready 14.546
Then the Upgrader considers the system as up-to-date 10.835
# 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.711
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.058
After features/support/hooks.rb:326 0.773
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
36.054
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.826
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.426
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.863
But a current signing key is available on our website 0.000
When the network is plugged 0.067
And Tor is ready 18.444
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.369
After features/support/hooks.rb:326 0.649
After features/support/hooks.rb:100 0.000