Project Number Date
test_Tails_ISO_devel 3630 02 Jan 2025, 12:27

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:29.744 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
1:56.621
Before features/support/hooks.rb:269 0.005
Given a computer 0.193
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 29.164
When I start Tails from USB drive "old" with network unplugged 1:22.249
Then the boot device has safe access rights 2.944
And Tails is running from USB drive "old" 0.314
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.277
And I unplug USB drive "old" 0.212
After features/support/hooks.rb:326 3.548
After features/support/hooks.rb:100 0.007
Tags: @product
2:3.333
Before features/support/hooks.rb:269 0.004
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login 1:22.696
Then Tails is running from USB drive "old" 0.327
And I create a persistent partition 29.656
And I take note of which tps features are available 1.349
Then a Tails persistence partition exists on USB drive "old" 0.768
And I shutdown Tails and wait for the computer to power off 8.352
After features/support/hooks.rb:326 0.177
After features/support/hooks.rb:100 0.009
Tags: @product
2:56.154
Before features/support/hooks.rb:269 0.006
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.825
Then Tails is running from USB drive "old" 0.372
And all tps features are active 2.067
When I write some files expected to persist 1.873
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.211
And all persistence configuration files have safe access rights 0.396
And all persistent directories from the old Tails version have safe access rights 2.458
And I take note of which tps features are available 0.468
And I shutdown Tails and wait for the computer to power off 4.306
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.981
After features/support/hooks.rb:326 0.106
After features/support/hooks.rb:100 0.009
Tags: @product
2:25.176
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 11.126
And I log in to a new session 17.459
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.699
And I plug USB drive "to_upgrade" 2.435
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.466
Then the running Tails is installed on USB drive "to_upgrade" 19.547
And I unplug USB drive "to_upgrade" 0.217
And I unplug USB drive "__internal" 0.222
After features/support/hooks.rb:326 2.269
After features/support/hooks.rb:100 0.000
Tags: @product
2:11.379
Before features/support/hooks.rb:269 0.007
Given a computer 0.188
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.841
Then all tps features from the old Tails version are active 1.638
And Tails is running from USB drive "to_upgrade" 0.345
And the boot device has safe access rights 3.450
And the expected persistent files created with the old Tails version are present in the filesystem 1.468
And all persistent directories from the old Tails version have safe access rights 2.445
After features/support/hooks.rb:326 0.677
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:18.199
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 11.379
And no SquashFS delta is installed 0.090
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.395
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.271
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.438
When the network is plugged 0.083
And Tor is ready 20.864
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.456
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.828
Given I shutdown Tails and wait for the computer to power off 10.701
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.718
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.169
And the file system changes introduced in version 6.2~testoverlayfs are present 0.314
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.386
# 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.389
When the network is plugged 0.067
And Tor is ready 19.784
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.426
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.692
Given I shutdown Tails and wait for the computer to power off 4.236
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.413
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.469
And the file system changes introduced in version 6.3~testoverlayfs are present 0.491
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.305
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.258
When the network is plugged 0.070
And Tor is ready 18.358
Then the Upgrader considers the system as up-to-date 0.296
# 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.686
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.919
After features/support/hooks.rb:326 0.818
After features/support/hooks.rb:100 0.060
Tags: @product @automatic_upgrade
38.881
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 9.678
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.331
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the signing key used by the Upgrader is outdated 0.815
But a current signing key is available on our website 0.000
When the network is plugged 0.086
And Tor is ready 21.177
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.721
After features/support/hooks.rb:326 0.833
After features/support/hooks.rb:100 0.000