Project Number Date
test_Tails_ISO_stable 5415 24 Jan 2025, 02:16

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:35.817 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:16.686
Before features/support/hooks.rb:269 0.003
Given a computer 0.209
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 38.461
When I start Tails from USB drive "old" with network unplugged 1:31.616
Then the boot device has safe access rights 3.962
And Tails is running from USB drive "old" 0.465
And there is no persistence partition on USB drive "old" 0.097
And process "udev-watchdog" is running 0.114
And udev-watchdog is monitoring the correct device 0.424
And I unplug USB drive "old" 0.230
After features/support/hooks.rb:326 3.683
After features/support/hooks.rb:100 0.026
Tags: @product
2:11.888
Before features/support/hooks.rb:269 0.006
Given a computer 0.238
And I start Tails from USB drive "old" with network unplugged and I login 1:28.776
Then Tails is running from USB drive "old" 0.498
And I create a persistent partition 31.965
And I take note of which tps features are available 1.279
Then a Tails persistence partition exists on USB drive "old" 0.893
And I shutdown Tails and wait for the computer to power off 8.236
After features/support/hooks.rb:326 0.177
After features/support/hooks.rb:100 0.009
Tags: @product
3:2.287
Before features/support/hooks.rb:269 0.006
Given a computer 0.467
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.936
Then Tails is running from USB drive "old" 0.835
And all tps features are active 2.298
When I write some files expected to persist 2.131
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.249
And all persistence configuration files have safe access rights 0.423
And all persistent directories from the old Tails version have safe access rights 2.721
And I take note of which tps features are available 0.509
And I shutdown Tails and wait for the computer to power off 4.385
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.326
After features/support/hooks.rb:326 0.119
After features/support/hooks.rb:100 0.009
Tags: @product
2:28.476
Before features/support/hooks.rb:269 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 10.568
And I log in to a new session 19.837
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.983
And I plug USB drive "to_upgrade" 2.441
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.228
Then the running Tails is installed on USB drive "to_upgrade" 18.979
And I unplug USB drive "to_upgrade" 0.214
And I unplug USB drive "__internal" 0.222
After features/support/hooks.rb:326 3.446
After features/support/hooks.rb:100 0.000
Tags: @product
2:9.385
Before features/support/hooks.rb:269 0.004
Given a computer 0.218
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:59.200
Then all tps features from the old Tails version are active 1.815
And Tails is running from USB drive "to_upgrade" 0.366
And the boot device has safe access rights 3.258
And the expected persistent files created with the old Tails version are present in the filesystem 1.477
And all persistent directories from the old Tails version have safe access rights 3.049
After features/support/hooks.rb:326 1.092
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:46.245
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.864
And no SquashFS delta is installed 0.104
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.327
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.144
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.478
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.449
When the network is plugged 0.086
And Tor is ready 22.036
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.283
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.077
Given I shutdown Tails and wait for the computer to power off 8.656
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.711
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.395
And the file system changes introduced in version 6.2~testoverlayfs are present 0.396
And only the 6.2~testoverlayfs SquashFS delta is installed 0.108
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.462
# 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.301
When the network is plugged 0.067
And Tor is ready 18.957
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.896
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.736
Given I shutdown Tails and wait for the computer to power off 4.162
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.354
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.187
And the file system changes introduced in version 6.3~testoverlayfs are present 0.564
And only the 6.3~testoverlayfs SquashFS delta is installed 0.081
# 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.381
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.305
When the network is plugged 0.069
And Tor is ready 17.351
Then the Upgrader considers the system as up-to-date 10.850
# 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.384
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.976
After features/support/hooks.rb:326 0.854
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
40.847
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.535
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.434
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 0.074
But a current signing key is available on our website 0.000
When the network is plugged 0.113
And Tor is ready 20.789
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.849
After features/support/hooks.rb:326 0.785
After features/support/hooks.rb:100 0.000