Project Number Date
test_Tails_ISO_devel 3841 28 May 2025, 13:17

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 20:25.183 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:21.867
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.228
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 31.278
When I start Tails from USB drive "old" with network unplugged 1:44.735
Then the boot device has safe access rights 3.399
And Tails is running from USB drive "old" 0.368
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.107
And udev-watchdog is monitoring the correct device 0.357
And I unplug USB drive "old" 0.215
After features/support/hooks.rb:330 3.755
After features/support/hooks.rb:100 0.010
Tags: @product
2:20.158
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login 1:36.968
Then Tails is running from USB drive "old" 0.369
And I create a persistent partition 32.733
And I take note of which tps features are available 2.188
Then a Tails persistence partition exists on USB drive "old" 0.935
And I shutdown Tails and wait for the computer to power off 6.765
After features/support/hooks.rb:330 0.157
After features/support/hooks.rb:100 0.010
Tags: @product
3:0.011
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.196
Then Tails is running from USB drive "old" 0.355
And all tps features are active 1.849
When I write some files expected to persist 1.862
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.788
And all persistence configuration files have safe access rights 0.437
And all persistent directories from the old Tails version have safe access rights 2.734
And I take note of which tps features are available 0.419
And I shutdown Tails and wait for the computer to power off 6.523
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.640
After features/support/hooks.rb:330 0.234
After features/support/hooks.rb:100 0.009
Tags: @product
2:41.278
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 without a persistent partition and stopped at Tails Greeter's login screen 11.933
And I log in to a new session 19.542
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.089
And I plug USB drive "to_upgrade" 2.535
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.212
Then the running Tails is installed on USB drive "to_upgrade" 27.536
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.223
After features/support/hooks.rb:330 6.921
After features/support/hooks.rb:100 0.000
Tags: @product
2:30.122
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.190
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:20.242
Then all tps features from the old Tails version are active 1.773
And Tails is running from USB drive "to_upgrade" 0.351
And the boot device has safe access rights 3.592
And the expected persistent files created with the old Tails version are present in the filesystem 1.372
And all persistent directories from the old Tails version have safe access rights 2.599
After features/support/hooks.rb:330 1.372
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:52.327
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 13.123
And no SquashFS delta is installed 0.117
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.549
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.092
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.427
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.472
When the network is plugged 0.067
And Tor is ready 20.987
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.696
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.395
Given I shutdown Tails and wait for the computer to power off 11.273
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.781
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.093
And the file system changes introduced in version 6.2~testoverlayfs are present 0.412
And only the 6.2~testoverlayfs SquashFS delta is installed 0.084
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.398
# 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.296
When the network is plugged 0.070
And Tor is ready 18.675
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.363
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 12.153
Given I shutdown Tails and wait for the computer to power off 4.372
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.941
Then Tails is running version 6.3~testoverlayfs 0.020
And all tps features are active 2.355
And the file system changes introduced in version 6.3~testoverlayfs are present 0.587
And only the 6.3~testoverlayfs SquashFS delta is installed 0.083
# 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.379
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.375
When the network is plugged 0.069
And Tor is ready 20.215
Then the Upgrader considers the system as up-to-date 0.351
# 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.097
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.930
After features/support/hooks.rb:330 0.703
After features/support/hooks.rb:100 0.041
Tags: @product @automatic_upgrade
39.417
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.017
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.923
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.382
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the signing key used by the Upgrader is outdated 0.159
But a current signing key is available on our website 0.000
When the network is plugged 0.083
And Tor is ready 19.183
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.618
After features/support/hooks.rb:330 0.913
After features/support/hooks.rb:100 0.000