Project Number Date
test_Tails_ISO_stable 5195 18 Oct 2024, 00: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 19:7.402 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:15.059
Before features/support/hooks.rb:269 0.006
Given a computer 0.249
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 36.643
When I start Tails from USB drive "old" with network unplugged 1:32.594
Then the boot device has safe access rights 3.360
And Tails is running from USB drive "old" 0.377
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.122
And udev-watchdog is monitoring the correct device 0.343
And I unplug USB drive "old" 0.192
After features/support/hooks.rb:326 7.540
After features/support/hooks.rb:100 0.007
Tags: @product
2:7.755
Before features/support/hooks.rb:269 0.007
Given a computer 0.228
And I start Tails from USB drive "old" with network unplugged and I login 1:22.871
Then Tails is running from USB drive "old" 0.386
And I create a persistent partition 33.340
And I take note of which tps features are available 1.559
Then a Tails persistence partition exists on USB drive "old" 0.874
And I shutdown Tails and wait for the computer to power off 8.493
After features/support/hooks.rb:326 0.204
After features/support/hooks.rb:100 0.008
Tags: @product
2:53.840
Before features/support/hooks.rb:269 0.004
Given a computer 0.197
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.913
Then Tails is running from USB drive "old" 0.810
And all tps features are active 2.179
When I write some files expected to persist 1.674
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.197
And all persistence configuration files have safe access rights 0.376
And all persistent directories from the old Tails version have safe access rights 3.528
And I take note of which tps features are available 0.486
And I shutdown Tails and wait for the computer to power off 4.449
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.025
After features/support/hooks.rb:326 0.117
After features/support/hooks.rb:100 0.011
Tags: @product
2:30.624
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.620
And I log in to a new session 19.499
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.893
And I plug USB drive "to_upgrade" 2.450
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.273
Then the running Tails is installed on USB drive "to_upgrade" 19.416
And I unplug USB drive "to_upgrade" 0.199
And I unplug USB drive "__internal" 0.271
After features/support/hooks.rb:326 3.604
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.027
Before features/support/hooks.rb:269 0.005
Given a computer 0.179
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.109
Then all tps features from the old Tails version are active 1.826
And Tails is running from USB drive "to_upgrade" 0.348
And the boot device has safe access rights 3.587
And the expected persistent files created with the old Tails version are present in the filesystem 1.496
And all persistent directories from the old Tails version have safe access rights 2.479
After features/support/hooks.rb:326 0.741
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:27.968
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 12.888
And no SquashFS delta is installed 0.661
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.483
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.305
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.416
When the network is plugged 0.071
And Tor is ready 20.766
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.072
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.447
Given I shutdown Tails and wait for the computer to power off 11.391
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.498
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 5.553
And the file system changes introduced in version 6.2~testoverlayfs are present 0.337
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.302
# 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.350
When the network is plugged 0.096
And Tor is ready 17.403
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.997
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.398
Given I shutdown Tails and wait for the computer to power off 4.431
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.251
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.121
And the file system changes introduced in version 6.3~testoverlayfs are present 0.531
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.336
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.288
When the network is plugged 0.065
And Tor is ready 16.680
Then the Upgrader considers the system as up-to-date 0.321
# 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.345
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.904
After features/support/hooks.rb:326 0.741
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
39.127
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.282
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.138
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 1.241
But a current signing key is available on our website 0.000
When the network is plugged 0.090
And Tor is ready 17.391
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.919
After features/support/hooks.rb:326 1.053
After features/support/hooks.rb:100 0.000