Project Number Date
test_Tails_ISO_stable 5587 22 Apr 2025, 13: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 23:28.296 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:51.956
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.287
And I create a 7200 MiB disk named "old" 0.106
And I plug USB drive "old" 1.068
And I write an old version of the Tails USB image to disk "old" 1:5.307
When I start Tails from USB drive "old" with network unplugged 1:40.604
Then the boot device has safe access rights 3.476
And Tails is running from USB drive "old" 0.345
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.104
And udev-watchdog is monitoring the correct device 0.362
And I unplug USB drive "old" 0.215
After features/support/hooks.rb:330 4.249
After features/support/hooks.rb:100 0.009
Tags: @product
2:24.570
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 1.897
And I start Tails from USB drive "old" with network unplugged and I login 1:34.964
Then Tails is running from USB drive "old" 0.437
And I create a persistent partition 35.098
And I take note of which tps features are available 2.624
Then a Tails persistence partition exists on USB drive "old" 0.982
And I shutdown Tails and wait for the computer to power off 8.566
After features/support/hooks.rb:330 0.190
After features/support/hooks.rb:100 0.008
Tags: @product
3:23.648
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.231
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:30.789
Then Tails is running from USB drive "old" 2.139
And all tps features are active 7.242
When I write some files expected to persist 3.822
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.239
And all persistence configuration files have safe access rights 0.400
And all persistent directories from the old Tails version have safe access rights 2.640
And I take note of which tps features are available 3.068
And I shutdown Tails and wait for the computer to power off 6.498
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.577
After features/support/hooks.rb:330 0.231
After features/support/hooks.rb:100 0.014
Tags: @product
3:9.777
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 25.050
And I log in to a new session 21.768
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.863
And I plug USB drive "to_upgrade" 2.440
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:45.153
Then the running Tails is installed on USB drive "to_upgrade" 32.918
And I unplug USB drive "to_upgrade" 0.273
And I unplug USB drive "__internal" 0.308
After features/support/hooks.rb:330 1.482
After features/support/hooks.rb:100 0.000
Tags: @product
2:49.323
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.312
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:37.785
Then all tps features from the old Tails version are active 1.950
And Tails is running from USB drive "to_upgrade" 0.387
And the boot device has safe access rights 4.069
And the expected persistent files created with the old Tails version are present in the filesystem 1.845
And all persistent directories from the old Tails version have safe access rights 2.972
After features/support/hooks.rb:330 1.117
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
8:6.525
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 36.166
And no SquashFS delta is installed 0.114
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.606
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.137
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.475
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.615
When the network is plugged 0.095
And Tor is ready 25.265
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.391
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.117
Given I shutdown Tails and wait for the computer to power off 11.053
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:30.411
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.684
And the file system changes introduced in version 6.2~testoverlayfs are present 0.372
And only the 6.2~testoverlayfs SquashFS delta is installed 0.086
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.447
# 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.297
When the network is plugged 0.113
And Tor is ready 19.461
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.261
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.647
Given I shutdown Tails and wait for the computer to power off 7.100
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:23.105
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.296
And the file system changes introduced in version 6.3~testoverlayfs are present 0.534
And only the 6.3~testoverlayfs SquashFS delta is installed 0.078
# 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.346
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.316
When the network is plugged 0.077
And Tor is ready 20.419
Then the Upgrader considers the system as up-to-date 0.488
# 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 18.501
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.406
After features/support/hooks.rb:330 0.845
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
42.492
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.288
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.816
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.086
And the signing key used by the Upgrader is outdated 0.122
But a current signing key is available on our website 0.000
When the network is plugged 0.111
And Tor is ready 21.461
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.607
After features/support/hooks.rb:330 0.716
After features/support/hooks.rb:100 0.000