Project Number Date
test_Tails_ISO_devel 3818 18 May 2025, 10:11

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:58.623 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:8.608
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.197
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 34.222
When I start Tails from USB drive "old" with network unplugged 1:29.178
Then the boot device has safe access rights 2.963
And Tails is running from USB drive "old" 0.324
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.284
And I unplug USB drive "old" 0.181
After features/support/hooks.rb:330 3.822
After features/support/hooks.rb:100 0.008
Tags: @product
2:12.434
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login 1:29.895
Then Tails is running from USB drive "old" 0.368
And I create a persistent partition 31.237
And I take note of which tps features are available 1.688
Then a Tails persistence partition exists on USB drive "old" 0.752
And I shutdown Tails and wait for the computer to power off 8.292
After features/support/hooks.rb:330 0.130
After features/support/hooks.rb:100 0.009
Tags: @product
3:7.816
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:31.400
Then Tails is running from USB drive "old" 0.358
And all tps features are active 2.049
When I write some files expected to persist 1.825
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.208
And all persistence configuration files have safe access rights 0.417
And all persistent directories from the old Tails version have safe access rights 2.535
And I take note of which tps features are available 0.436
And I shutdown Tails and wait for the computer to power off 4.437
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.938
After features/support/hooks.rb:330 0.105
After features/support/hooks.rb:100 0.009
Tags: @product
2:26.920
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.015
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.256
And I log in to a new session 18.554
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.543
And I plug USB drive "to_upgrade" 2.464
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.389
Then the running Tails is installed on USB drive "to_upgrade" 19.309
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.200
After features/support/hooks.rb:330 1.972
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.229
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.192
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.365
Then all tps features from the old Tails version are active 3.123
And Tails is running from USB drive "to_upgrade" 0.439
And the boot device has safe access rights 3.207
And the expected persistent files created with the old Tails version are present in the filesystem 1.413
And all persistent directories from the old Tails version have safe access rights 2.489
After features/support/hooks.rb:330 0.996
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:12.988
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.636
And no SquashFS delta is installed 0.106
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.345
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.336
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.460
When the network is plugged 0.065
And Tor is ready 22.503
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.398
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.626
Given I shutdown Tails and wait for the computer to power off 8.673
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:20.078
Then Tails is running version 6.2~testoverlayfs 0.037
And all tps features are active 2.603
And the file system changes introduced in version 6.2~testoverlayfs are present 0.428
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.316
# 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.279
When the network is plugged 0.081
And Tor is ready 47.954
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.594
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.927
Given I shutdown Tails and wait for the computer to power off 6.451
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.037
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.127
And the file system changes introduced in version 6.3~testoverlayfs are present 0.496
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.310
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.282
When the network is plugged 0.073
And Tor is ready 17.899
Then the Upgrader considers the system as up-to-date 0.288
# 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 16.468
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.877
After features/support/hooks.rb:330 0.726
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
34.625
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.913
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.388
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the signing key used by the Upgrader is outdated 0.087
But a current signing key is available on our website 0.000
When the network is plugged 0.065
And Tor is ready 16.024
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.074
After features/support/hooks.rb:330 0.759
After features/support/hooks.rb:100 0.000