Project Number Date
test_Tails_ISO_devel 3766 04 Apr 2025, 13:02

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:45.059 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:3.325
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.185
And I create a 7200 MiB disk named "old" 0.039
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 29.671
When I start Tails from USB drive "old" with network unplugged 1:28.522
Then the boot device has safe access rights 2.865
And Tails is running from USB drive "old" 0.353
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.293
And I unplug USB drive "old" 0.180
After features/support/hooks.rb:330 3.506
After features/support/hooks.rb:100 0.011
Tags: @product
2:4.552
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login 1:22.645
Then Tails is running from USB drive "old" 0.316
And I create a persistent partition 30.601
And I take note of which tps features are available 1.755
Then a Tails persistence partition exists on USB drive "old" 0.772
And I shutdown Tails and wait for the computer to power off 8.275
After features/support/hooks.rb:330 0.165
After features/support/hooks.rb:100 0.009
Tags: @product
2:53.509
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.247
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.770
Then Tails is running from USB drive "old" 0.429
And all tps features are active 1.875
When I write some files expected to persist 1.603
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.216
And all persistence configuration files have safe access rights 0.357
And all persistent directories from the old Tails version have safe access rights 2.397
And I take note of which tps features are available 0.363
And I shutdown Tails and wait for the computer to power off 4.320
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.927
After features/support/hooks.rb:330 0.154
After features/support/hooks.rb:100 0.010
Tags: @product
2:32.137
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.244
And I log in to a new session 20.173
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.707
And I plug USB drive "to_upgrade" 2.429
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.165
Then the running Tails is installed on USB drive "to_upgrade" 23.026
And I unplug USB drive "to_upgrade" 0.196
And I unplug USB drive "__internal" 0.193
After features/support/hooks.rb:330 2.367
After features/support/hooks.rb:100 0.000
Tags: @product
2:10.095
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.188
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:0.897
Then all tps features from the old Tails version are active 1.565
And Tails is running from USB drive "to_upgrade" 0.302
And the boot device has safe access rights 3.168
And the expected persistent files created with the old Tails version are present in the filesystem 1.406
And all persistent directories from the old Tails version have safe access rights 2.566
After features/support/hooks.rb:330 1.352
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:26.026
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 11.654
And no SquashFS delta is installed 0.161
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.363
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.121
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.353
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.447
When the network is plugged 0.069
And Tor is ready 21.924
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.492
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.288
Given I shutdown Tails and wait for the computer to power off 8.499
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.792
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.018
And the file system changes introduced in version 6.2~testoverlayfs are present 0.293
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.311
# 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.358
When the network is plugged 0.108
And Tor is ready 19.493
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.299
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.313
Given I shutdown Tails and wait for the computer to power off 4.241
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.045
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.936
And the file system changes introduced in version 6.3~testoverlayfs are present 0.477
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.299
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.263
When the network is plugged 0.070
And Tor is ready 18.700
Then the Upgrader considers the system as up-to-date 0.386
# 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 15.499
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.573
After features/support/hooks.rb:330 0.705
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
35.411
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.422
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.341
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 0.074
But a current signing key is available on our website 0.000
When the network is plugged 0.063
And Tor is ready 17.630
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.821
After features/support/hooks.rb:330 0.635
After features/support/hooks.rb:100 0.000