Project Number Date
test_Tails_ISO_20898-tinyrpc-drop 1 15 Apr 2025, 21:35

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 21:21.466 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:14.030
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.247
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.065
And I write an old version of the Tails USB image to disk "old" 32.327
When I start Tails from USB drive "old" with network unplugged 1:36.157
Then the boot device has safe access rights 3.161
And Tails is running from USB drive "old" 0.331
And there is no persistence partition on USB drive "old" 0.084
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.283
And I unplug USB drive "old" 0.228
After features/support/hooks.rb:330 3.796
After features/support/hooks.rb:100 0.012
Tags: @product
2:14.413
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login 1:28.940
Then Tails is running from USB drive "old" 0.407
And I create a persistent partition 31.753
And I take note of which tps features are available 2.443
Then a Tails persistence partition exists on USB drive "old" 1.821
And I shutdown Tails and wait for the computer to power off 8.853
After features/support/hooks.rb:330 0.196
After features/support/hooks.rb:100 0.010
Tags: @product
3:1.469
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.212
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.773
Then Tails is running from USB drive "old" 0.519
And all tps features are active 2.243
When I write some files expected to persist 1.675
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.210
And all persistence configuration files have safe access rights 0.377
And all persistent directories from the old Tails version have safe access rights 2.441
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.304
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.242
After features/support/hooks.rb:330 0.149
After features/support/hooks.rb:100 0.008
Tags: @product
2:44.083
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.620
And I log in to a new session 21.640
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.676
And I plug USB drive "to_upgrade" 2.731
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.409
Then the running Tails is installed on USB drive "to_upgrade" 28.546
And I unplug USB drive "to_upgrade" 0.245
And I unplug USB drive "__internal" 0.212
After features/support/hooks.rb:330 2.749
After features/support/hooks.rb:100 0.000
Tags: @product
2:45.314
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.214
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:32.264
Then all tps features from the old Tails version are active 2.287
And Tails is running from USB drive "to_upgrade" 0.523
And the boot device has safe access rights 4.442
And the expected persistent files created with the old Tails version are present in the filesystem 1.988
And all persistent directories from the old Tails version have safe access rights 3.594
After features/support/hooks.rb:330 1.952
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
7:38.138
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 29.331
And no SquashFS delta is installed 0.176
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.649
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.138
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.707
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.684
When the network is plugged 0.178
And Tor is ready 24.155
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.803
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.293
Given I shutdown Tails and wait for the computer to power off 9.176
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.299
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.841
And the file system changes introduced in version 6.2~testoverlayfs are present 0.473
And only the 6.2~testoverlayfs SquashFS delta is installed 0.093
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.693
# 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.514
When the network is plugged 0.105
And Tor is ready 19.712
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.311
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.773
Given I shutdown Tails and wait for the computer to power off 6.517
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:22.043
Then Tails is running version 6.3~testoverlayfs 0.021
And all tps features are active 3.468
And the file system changes introduced in version 6.3~testoverlayfs are present 0.836
And only the 6.3~testoverlayfs SquashFS delta is installed 0.147
# 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.480
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.415
When the network is plugged 0.118
And Tor is ready 21.205
Then the Upgrader considers the system as up-to-date 0.413
# 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 17.298
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.037
After features/support/hooks.rb:330 0.862
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
44.017
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 13.009
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.485
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.104
And the signing key used by the Upgrader is outdated 0.109
But a current signing key is available on our website 0.000
When the network is plugged 0.121
And Tor is ready 21.743
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.441
After features/support/hooks.rb:330 1.256
After features/support/hooks.rb:100 0.000