Project Number Date
test_Tails_ISO_devel 3726 06 Mar 2025, 13:05

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 19:10.629 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:2.208
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.197
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 34.211
When I start Tails from USB drive "old" with network unplugged 1:22.856
Then the boot device has safe access rights 2.915
And Tails is running from USB drive "old" 0.310
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.087
And udev-watchdog is monitoring the correct device 0.285
And I unplug USB drive "old" 0.181
After features/support/hooks.rb:330 6.970
After features/support/hooks.rb:100 0.008
Tags: @product
2:3.714
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.211
And I start Tails from USB drive "old" with network unplugged and I login 1:21.324
Then Tails is running from USB drive "old" 0.330
And I create a persistent partition 31.318
And I take note of which tps features are available 1.420
Then a Tails persistence partition exists on USB drive "old" 0.753
And I shutdown Tails and wait for the computer to power off 8.354
After features/support/hooks.rb:330 0.311
After features/support/hooks.rb:100 0.009
Tags: @product
2:57.471
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.294
Then Tails is running from USB drive "old" 1.759
And all tps features are active 2.166
When I write some files expected to persist 1.816
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.293
And all persistence configuration files have safe access rights 0.442
And all persistent directories from the old Tails version have safe access rights 5.102
And I take note of which tps features are available 0.660
And I shutdown Tails and wait for the computer to power off 6.233
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.493
After features/support/hooks.rb:330 0.141
After features/support/hooks.rb:100 0.012
Tags: @product
2:36.126
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 without a persistent partition and stopped at Tails Greeter's login screen 14.380
And I log in to a new session 19.810
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.480
And I plug USB drive "to_upgrade" 2.396
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.706
Then the running Tails is installed on USB drive "to_upgrade" 22.922
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.222
After features/support/hooks.rb:330 3.362
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.494
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.226
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.667
Then all tps features from the old Tails version are active 1.616
And Tails is running from USB drive "to_upgrade" 0.376
And the boot device has safe access rights 3.554
And the expected persistent files created with the old Tails version are present in the filesystem 1.551
And all persistent directories from the old Tails version have safe access rights 2.501
After features/support/hooks.rb:330 1.396
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:37.517
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.451
And no SquashFS delta is installed 0.161
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.515
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.085
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.369
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.487
When the network is plugged 0.102
And Tor is ready 21.552
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.792
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.026
Given I shutdown Tails and wait for the computer to power off 9.301
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.199
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.193
And the file system changes introduced in version 6.2~testoverlayfs are present 0.307
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.307
# 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.310
When the network is plugged 0.075
And Tor is ready 19.847
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.457
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.680
Given I shutdown Tails and wait for the computer to power off 6.573
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.376
Then Tails is running version 6.3~testoverlayfs 0.067
And all tps features are active 2.366
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.118
# 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.423
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.424
When the network is plugged 0.141
And Tor is ready 18.547
Then the Upgrader considers the system as up-to-date 0.329
# 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.350
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.943
After features/support/hooks.rb:330 0.683
After features/support/hooks.rb:100 0.059
Tags: @product @automatic_upgrade
37.095
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 10.517
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.226
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.085
And the signing key used by the Upgrader is outdated 0.071
But a current signing key is available on our website 0.000
When the network is plugged 0.073
And Tor is ready 18.428
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.693
After features/support/hooks.rb:330 0.857
After features/support/hooks.rb:100 0.000