Project Number Date
test_Tails_ISO_devel 3770 07 Apr 2025, 16:58

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:51.127 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:7.974
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.208
And I create a 7200 MiB disk named "old" 0.036
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 29.547
When I start Tails from USB drive "old" with network unplugged 1:33.162
Then the boot device has safe access rights 3.014
And Tails is running from USB drive "old" 0.319
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.286
And I unplug USB drive "old" 0.183
After features/support/hooks.rb:330 7.093
After features/support/hooks.rb:100 0.009
Tags: @product
2:6.242
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login 1:23.703
Then Tails is running from USB drive "old" 0.316
And I create a persistent partition 31.250
And I take note of which tps features are available 1.799
Then a Tails persistence partition exists on USB drive "old" 0.754
And I shutdown Tails and wait for the computer to power off 8.235
After features/support/hooks.rb:330 0.131
After features/support/hooks.rb:100 0.009
Tags: @product
2:53.141
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.075
Then Tails is running from USB drive "old" 0.345
And all tps features are active 1.959
When I write some files expected to persist 1.861
# 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.368
And all persistent directories from the old Tails version have safe access rights 2.257
And I take note of which tps features are available 0.362
And I shutdown Tails and wait for the computer to power off 4.667
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 22.845
After features/support/hooks.rb:330 0.117
After features/support/hooks.rb:100 0.010
Tags: @product
2:27.461
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 10.830
And I log in to a new session 18.540
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.818
And I plug USB drive "to_upgrade" 2.399
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.284
Then the running Tails is installed on USB drive "to_upgrade" 19.188
And I unplug USB drive "to_upgrade" 0.199
And I unplug USB drive "__internal" 0.200
After features/support/hooks.rb:330 3.033
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.896
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.183
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.852
Then all tps features from the old Tails version are active 1.585
And Tails is running from USB drive "to_upgrade" 0.308
And the boot device has safe access rights 3.304
And the expected persistent files created with the old Tails version are present in the filesystem 1.364
And all persistent directories from the old Tails version have safe access rights 2.296
After features/support/hooks.rb:330 1.298
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:24.913
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.148
And no SquashFS delta is installed 0.161
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.287
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.518
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.503
When the network is plugged 0.082
And Tor is ready 21.231
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.029
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.204
Given I shutdown Tails and wait for the computer to power off 8.364
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.466
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 1.985
And the file system changes introduced in version 6.2~testoverlayfs are present 0.272
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.319
# 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.281
When the network is plugged 0.057
And Tor is ready 17.667
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.810
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.415
Given I shutdown Tails and wait for the computer to power off 4.204
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.606
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.942
And the file system changes introduced in version 6.3~testoverlayfs are present 0.539
And only the 6.3~testoverlayfs SquashFS delta is installed 0.080
# 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.328
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.287
When the network is plugged 0.061
And Tor is ready 18.206
Then the Upgrader considers the system as up-to-date 0.298
# 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.826
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.556
After features/support/hooks.rb:330 0.695
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
37.496
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 9.151
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.324
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 0.068
But a current signing key is available on our website 0.000
When the network is plugged 0.089
And Tor is ready 20.092
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.706
After features/support/hooks.rb:330 0.883
After features/support/hooks.rb:100 0.000