Project Number Date
test_Tails_ISO_stable 4882 11 Jun 2024, 12:57

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.038 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:23.691
Before features/support/hooks.rb:269 0.009
Given a computer 0.219
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 35.007
When I start Tails from USB drive "old" with network unplugged 1:43.056
Then the boot device has safe access rights 3.252
And Tails is running from USB drive "old" 0.320
And there is no persistence partition on USB drive "old" 0.054
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.277
And I unplug USB drive "old" 0.311
After features/support/hooks.rb:315 4.239
After features/support/hooks.rb:100 0.058
Tags: @product
2:21.178
Before features/support/hooks.rb:269 0.008
Given a computer 0.231
And I start Tails from USB drive "old" with network unplugged and I login 1:33.759
Then Tails is running from USB drive "old" 0.406
And I create a persistent partition 34.814
And I take note of which tps features are available 2.157
Then a Tails persistence partition exists on USB drive "old" 0.889
And I shutdown Tails and wait for the computer to power off 8.918
After features/support/hooks.rb:315 0.136
After features/support/hooks.rb:100 0.011
Tags: @product
2:53.565
Before features/support/hooks.rb:269 0.006
Given a computer 0.273
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.878
Then Tails is running from USB drive "old" 0.378
And all tps features are active 2.295
When I write some files expected to persist 1.897
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.212
And all persistence configuration files have safe access rights 0.402
And all persistent directories from the old Tails version have safe access rights 2.962
And I take note of which tps features are available 0.591
And I shutdown Tails and wait for the computer to power off 4.637
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.035
After features/support/hooks.rb:315 0.101
After features/support/hooks.rb:100 0.011
Tags: @product
2:29.605
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 12.465
And I log in to a new session 18.219
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.481
And I plug USB drive "to_upgrade" 2.383
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.874
Then the running Tails is installed on USB drive "to_upgrade" 17.718
And I unplug USB drive "to_upgrade" 0.228
And I unplug USB drive "__internal" 0.234
After features/support/hooks.rb:315 2.720
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.779
Before features/support/hooks.rb:269 0.007
Given a computer 0.353
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.788
Then all tps features from the old Tails version are active 1.671
And Tails is running from USB drive "to_upgrade" 0.332
And the boot device has safe access rights 3.362
And the expected persistent files created with the old Tails version are present in the filesystem 1.680
And all persistent directories from the old Tails version have safe access rights 2.591
After features/support/hooks.rb:315 0.980
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:40.019
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.867
And no SquashFS delta is installed 0.344
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.633
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.328
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.494
When the network is plugged 0.046
And Tor is ready 19.315
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.598
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.552
Given I shutdown Tails and wait for the computer to power off 10.952
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.875
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.675
And the file system changes introduced in version 6.2~testoverlayfs are present 0.508
And only the 6.2~testoverlayfs SquashFS delta is installed 0.064
# 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.319
When the network is plugged 0.038
And Tor is ready 19.924
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.197
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.650
Given I shutdown Tails and wait for the computer to power off 4.276
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.571
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.243
And the file system changes introduced in version 6.3~testoverlayfs are present 0.582
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.339
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.282
When the network is plugged 0.045
And Tor is ready 20.236
Then the Upgrader considers the system as up-to-date 0.330
# 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.155
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.032
After features/support/hooks.rb:315 0.836
After features/support/hooks.rb:100 0.039
Tags: @product @automatic_upgrade
37.198
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 9.960
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.485
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.077
And the signing key used by the Upgrader is outdated 1.035
But a current signing key is available on our website 0.000
When the network is plugged 0.035
And Tor is ready 17.805
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.797
After features/support/hooks.rb:315 0.893
After features/support/hooks.rb:100 0.000