Project Number Date
test_Tails_ISO_stable 5290 25 Nov 2024, 16:30

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:10.098 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:19.160
Before features/support/hooks.rb:269 0.006
Given a computer 0.204
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 31.541
When I start Tails from USB drive "old" with network unplugged 1:42.050
Then the boot device has safe access rights 3.188
And Tails is running from USB drive "old" 0.347
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.121
And udev-watchdog is monitoring the correct device 0.344
And I unplug USB drive "old" 0.191
After features/support/hooks.rb:326 10.349
After features/support/hooks.rb:100 0.008
Tags: @product
2:15.042
Before features/support/hooks.rb:269 0.006
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login 1:28.808
Then Tails is running from USB drive "old" 0.366
And I create a persistent partition 34.451
And I take note of which tps features are available 1.552
Then a Tails persistence partition exists on USB drive "old" 0.840
And I shutdown Tails and wait for the computer to power off 8.820
After features/support/hooks.rb:326 0.191
After features/support/hooks.rb:100 0.010
Tags: @product
3:2.062
Before features/support/hooks.rb:269 0.007
Given a computer 0.201
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:24.692
Then Tails is running from USB drive "old" 0.437
And all tps features are active 2.152
When I write some files expected to persist 1.996
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.234
And all persistence configuration files have safe access rights 0.438
And all persistent directories from the old Tails version have safe access rights 2.532
And I take note of which tps features are available 0.466
And I shutdown Tails and wait for the computer to power off 4.424
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.484
After features/support/hooks.rb:326 0.159
After features/support/hooks.rb:100 0.011
Tags: @product
2:38.613
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.561
And I log in to a new session 22.463
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.816
And I plug USB drive "to_upgrade" 2.507
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.251
Then the running Tails is installed on USB drive "to_upgrade" 23.548
And I unplug USB drive "to_upgrade" 0.232
And I unplug USB drive "__internal" 0.230
After features/support/hooks.rb:326 3.596
After features/support/hooks.rb:100 0.000
Tags: @product
2:23.532
Before features/support/hooks.rb:269 0.007
Given a computer 0.327
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.592
Then all tps features from the old Tails version are active 1.619
And Tails is running from USB drive "to_upgrade" 0.426
And the boot device has safe access rights 3.214
And the expected persistent files created with the old Tails version are present in the filesystem 1.658
And all persistent directories from the old Tails version have safe access rights 2.693
After features/support/hooks.rb:326 0.579
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:49.961
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.176
And no SquashFS delta is installed 0.303
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.460
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.081
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.318
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.480
When the network is plugged 0.068
And Tor is ready 23.258
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.402
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 15.337
Given I shutdown Tails and wait for the computer to power off 11.316
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.682
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.395
And the file system changes introduced in version 6.2~testoverlayfs are present 0.442
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.430
# 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.347
When the network is plugged 0.112
And Tor is ready 19.368
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.004
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.341
Given I shutdown Tails and wait for the computer to power off 4.466
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.431
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.171
And the file system changes introduced in version 6.3~testoverlayfs are present 0.494
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.365
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.409
When the network is plugged 0.087
And Tor is ready 16.179
Then the Upgrader considers the system as up-to-date 0.361
# 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.400
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.074
After features/support/hooks.rb:326 0.765
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
41.725
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.151
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.575
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the signing key used by the Upgrader is outdated 0.997
But a current signing key is available on our website 0.000
When the network is plugged 0.071
And Tor is ready 21.324
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.536
After features/support/hooks.rb:326 0.775
After features/support/hooks.rb:100 0.000