Project Number Date
test_Tails_ISO_devel 3625 28 Dec 2024, 12:21

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 18:37.904 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.667
Before features/support/hooks.rb:269 0.005
Given a computer 0.187
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 28.591
When I start Tails from USB drive "old" with network unplugged 1:29.818
Then the boot device has safe access rights 2.983
And Tails is running from USB drive "old" 0.320
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.303
And I unplug USB drive "old" 0.190
After features/support/hooks.rb:326 3.527
After features/support/hooks.rb:100 0.008
Tags: @product
2:5.210
Before features/support/hooks.rb:269 0.005
Given a computer 0.175
And I start Tails from USB drive "old" with network unplugged and I login 1:24.607
Then Tails is running from USB drive "old" 0.333
And I create a persistent partition 29.562
And I take note of which tps features are available 1.659
Then a Tails persistence partition exists on USB drive "old" 0.701
And I shutdown Tails and wait for the computer to power off 8.169
After features/support/hooks.rb:326 0.182
After features/support/hooks.rb:100 0.007
Tags: @product
2:45.692
Before features/support/hooks.rb:269 0.003
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:9.528
Then Tails is running from USB drive "old" 0.750
And all tps features are active 1.870
When I write some files expected to persist 1.688
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.199
And all persistence configuration files have safe access rights 0.348
And all persistent directories from the old Tails version have safe access rights 2.325
And I take note of which tps features are available 0.444
And I shutdown Tails and wait for the computer to power off 4.263
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.092
After features/support/hooks.rb:326 0.253
After features/support/hooks.rb:100 0.013
Tags: @product
2:38.685
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.655
And I log in to a new session 25.333
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.756
And I plug USB drive "to_upgrade" 2.475
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.532
Then the running Tails is installed on USB drive "to_upgrade" 18.519
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:326 2.442
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.258
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:5.122
Then all tps features from the old Tails version are active 1.624
And Tails is running from USB drive "to_upgrade" 0.303
And the boot device has safe access rights 3.093
And the expected persistent files created with the old Tails version are present in the filesystem 1.561
And all persistent directories from the old Tails version have safe access rights 2.374
After features/support/hooks.rb:326 0.744
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
6:15.200
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 11.616
And no SquashFS delta is installed 0.076
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.336
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.224
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.294
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.431
When the network is plugged 0.062
And Tor is ready 22.435
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.139
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.222
Given I shutdown Tails and wait for the computer to power off 8.568
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.583
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.317
And the file system changes introduced in version 6.2~testoverlayfs are present 0.283
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.309
# 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.257
When the network is plugged 0.081
And Tor is ready 21.453
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.044
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.629
Given I shutdown Tails and wait for the computer to power off 4.165
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.059
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.263
And the file system changes introduced in version 6.3~testoverlayfs are present 0.474
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.327
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.275
When the network is plugged 0.074
And Tor is ready 16.412
Then the Upgrader considers the system as up-to-date 0.307
# 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.955
After features/support/hooks.rb:326 0.875
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
35.190
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 10.181
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.348
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 0.731
But a current signing key is available on our website 0.000
When the network is plugged 0.084
And Tor is ready 18.798
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.979
After features/support/hooks.rb:326 1.095
After features/support/hooks.rb:100 0.000