Project Number Date
test_Tails_ISO_devel 3699 18 Feb 2025, 13:03

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 22:39.800 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:27.443
Before features/support/hooks.rb:269 0.006
Given a computer 0.198
And I create a 7200 MiB disk named "old" 0.055
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 38.126
When I start Tails from USB drive "old" with network unplugged 1:43.256
Then the boot device has safe access rights 3.619
And Tails is running from USB drive "old" 0.383
And there is no persistence partition on USB drive "old" 0.083
And process "udev-watchdog" is running 0.115
And udev-watchdog is monitoring the correct device 0.352
And I unplug USB drive "old" 0.197
After features/support/hooks.rb:326 3.896
After features/support/hooks.rb:100 0.013
Tags: @product
2:22.220
Before features/support/hooks.rb:269 0.007
Given a computer 0.362
And I start Tails from USB drive "old" with network unplugged and I login 1:32.468
Then Tails is running from USB drive "old" 0.405
And I create a persistent partition 37.384
And I take note of which tps features are available 2.096
Then a Tails persistence partition exists on USB drive "old" 0.881
And I shutdown Tails and wait for the computer to power off 8.622
After features/support/hooks.rb:326 0.341
After features/support/hooks.rb:100 0.011
Tags: @product
3:11.010
Before features/support/hooks.rb:269 0.006
Given a computer 0.276
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:30.962
Then Tails is running from USB drive "old" 0.583
And all tps features are active 2.726
When I write some files expected to persist 2.205
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.271
And all persistence configuration files have safe access rights 0.443
And all persistent directories from the old Tails version have safe access rights 2.770
And I take note of which tps features are available 0.656
And I shutdown Tails and wait for the computer to power off 4.569
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.544
After features/support/hooks.rb:326 0.120
After features/support/hooks.rb:100 0.012
Tags: @product
3:5.682
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 34.428
And I log in to a new session 21.707
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.308
And I plug USB drive "to_upgrade" 2.626
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.720
Then the running Tails is installed on USB drive "to_upgrade" 24.343
And I unplug USB drive "to_upgrade" 0.264
And I unplug USB drive "__internal" 0.282
After features/support/hooks.rb:326 7.106
After features/support/hooks.rb:100 0.000
Tags: @product
2:50.336
Before features/support/hooks.rb:269 0.007
Given a computer 0.451
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:39.866
Then all tps features from the old Tails version are active 1.794
And Tails is running from USB drive "to_upgrade" 0.466
And the boot device has safe access rights 3.721
And the expected persistent files created with the old Tails version are present in the filesystem 1.525
And all persistent directories from the old Tails version have safe access rights 2.510
After features/support/hooks.rb:326 0.697
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
8:2.122
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 31.987
And no SquashFS delta is installed 0.098
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.422
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.326
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.597
When the network is plugged 0.091
And Tor is ready 22.035
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.292
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.926
Given I shutdown Tails and wait for the computer to power off 11.126
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:19.595
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 3.397
And the file system changes introduced in version 6.2~testoverlayfs are present 0.558
And only the 6.2~testoverlayfs SquashFS delta is installed 0.096
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.378
# 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.402
When the network is plugged 0.080
And Tor is ready 19.641
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.928
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 12.705
Given I shutdown Tails and wait for the computer to power off 9.366
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:34.923
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 5.257
And the file system changes introduced in version 6.3~testoverlayfs are present 0.625
And only the 6.3~testoverlayfs SquashFS delta is installed 0.098
# 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.435
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.327
When the network is plugged 0.316
And Tor is ready 23.256
Then the Upgrader considers the system as up-to-date 0.352
# 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 16.998
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.376
After features/support/hooks.rb:326 0.979
After features/support/hooks.rb:100 0.032
Tags: @product @automatic_upgrade
40.984
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 14.110
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.342
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the signing key used by the Upgrader is outdated 0.089
But a current signing key is available on our website 0.000
When the network is plugged 0.698
And Tor is ready 19.982
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.686
After features/support/hooks.rb:326 1.398
After features/support/hooks.rb:100 0.000