Project Number Date
test_Tails_ISO_devel 3401 27 May 2024, 13:25

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 20:33.564 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
1:59.432
Before features/support/hooks.rb:259 0.008
Given a computer 0.181
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 28.246
When I start Tails from USB drive "old" with network unplugged 1:25.296
Then the boot device has safe access rights 3.459
And Tails is running from USB drive "old" 0.366
And there is no persistence partition on USB drive "old" 0.113
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.365
And I unplug USB drive "old" 0.203
After features/support/hooks.rb:305 7.197
After features/support/hooks.rb:89 0.011
Tags: @product
2:14.735
Before features/support/hooks.rb:259 0.008
Given a computer 0.271
And I start Tails from USB drive "old" with network unplugged and I login 1:27.296
Then Tails is running from USB drive "old" 0.400
And I create a persistent partition 35.333
And I take note of which tps features are available 1.795
Then a Tails persistence partition exists on USB drive "old" 0.851
And I shutdown Tails and wait for the computer to power off 8.785
After features/support/hooks.rb:305 0.200
After features/support/hooks.rb:89 0.013
Tags: @product
3:2.724
Before features/support/hooks.rb:259 0.006
Given a computer 0.282
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.623
Then Tails is running from USB drive "old" 0.340
And all tps features are active 2.078
When I write some files expected to persist 1.991
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.228
And all persistence configuration files have safe access rights 0.404
And all persistent directories from the old Tails version have safe access rights 2.487
And I take note of which tps features are available 0.508
And I shutdown Tails and wait for the computer to power off 4.795
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.982
After features/support/hooks.rb:305 0.136
After features/support/hooks.rb:89 0.010
Tags: @product
2:35.001
Before features/support/hooks.rb:259 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 11.424
And I log in to a new session 23.490
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.498
And I plug USB drive "to_upgrade" 2.454
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.687
Then the running Tails is installed on USB drive "to_upgrade" 20.017
And I unplug USB drive "to_upgrade" 0.240
And I unplug USB drive "__internal" 0.187
After features/support/hooks.rb:305 2.268
After features/support/hooks.rb:89 0.000
Tags: @product
2:32.454
Before features/support/hooks.rb:259 0.008
Given a computer 0.206
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:21.367
Then all tps features from the old Tails version are active 2.223
And Tails is running from USB drive "to_upgrade" 0.459
And the boot device has safe access rights 3.430
And the expected persistent files created with the old Tails version are present in the filesystem 1.744
And all persistent directories from the old Tails version have safe access rights 3.021
After features/support/hooks.rb:305 0.902
After features/support/hooks.rb:89 0.014
Tags: @product @automatic_upgrade
7:29.694
Before features/support/hooks.rb:259 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.997
And no SquashFS delta is installed 0.164
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.456
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.316
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.475
When the network is plugged 0.035
And Tor is ready 51.426
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.734
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.675
Given I shutdown Tails and wait for the computer to power off 8.612
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:20.138
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.414
And the file system changes introduced in version 6.2~testoverlayfs are present 0.399
And only the 6.2~testoverlayfs SquashFS delta is installed 0.076
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.366
# 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.284
When the network is plugged 0.037
And Tor is ready 17.811
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.590
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 13.010
Given I shutdown Tails and wait for the computer to power off 6.839
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.371
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.151
And the file system changes introduced in version 6.3~testoverlayfs are present 0.563
And only the 6.3~testoverlayfs SquashFS delta is installed 0.084
# 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.372
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.282
When the network is plugged 0.058
And Tor is ready 21.510
Then the Upgrader considers the system as up-to-date 0.328
# 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 15.026
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.997
After features/support/hooks.rb:305 0.786
After features/support/hooks.rb:89 0.019
Tags: @product @automatic_upgrade
39.521
Before features/support/hooks.rb:259 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.995
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.291
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 0.464
But a current signing key is available on our website 0.001
When the network is plugged 0.041
And Tor is ready 20.592
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.076
After features/support/hooks.rb:305 0.638
After features/support/hooks.rb:89 0.000