Project Number Date
test_Tails_ISO_devel 3748 21 Mar 2025, 13:08

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:7.732 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:9.083
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.231
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 31.706
When I start Tails from USB drive "old" with network unplugged 1:31.659
Then the boot device has safe access rights 3.297
And Tails is running from USB drive "old" 0.334
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.108
And udev-watchdog is monitoring the correct device 0.307
And I unplug USB drive "old" 0.259
After features/support/hooks.rb:330 3.810
After features/support/hooks.rb:100 0.009
Tags: @product
2:17.329
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login 1:29.569
Then Tails is running from USB drive "old" 0.330
And I create a persistent partition 36.246
And I take note of which tps features are available 1.628
Then a Tails persistence partition exists on USB drive "old" 0.806
And I shutdown Tails and wait for the computer to power off 8.539
After features/support/hooks.rb:330 0.216
After features/support/hooks.rb:100 0.009
Tags: @product
3:5.050
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.885
Then Tails is running from USB drive "old" 0.383
And all tps features are active 2.058
When I write some files expected to persist 2.270
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.245
And all persistence configuration files have safe access rights 0.432
And all persistent directories from the old Tails version have safe access rights 3.364
And I take note of which tps features are available 0.517
And I shutdown Tails and wait for the computer to power off 6.968
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.728
After features/support/hooks.rb:330 0.174
After features/support/hooks.rb:100 0.012
Tags: @product
2:36.961
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 14.341
And I log in to a new session 20.008
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.583
And I plug USB drive "to_upgrade" 2.500
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.770
Then the running Tails is installed on USB drive "to_upgrade" 20.286
And I unplug USB drive "to_upgrade" 0.210
And I unplug USB drive "__internal" 0.259
After features/support/hooks.rb:330 2.186
After features/support/hooks.rb:100 0.000
Tags: @product
2:35.127
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.204
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:25.018
Then all tps features from the old Tails version are active 2.093
And Tails is running from USB drive "to_upgrade" 0.322
And the boot device has safe access rights 3.461
And the expected persistent files created with the old Tails version are present in the filesystem 1.554
And all persistent directories from the old Tails version have safe access rights 2.473
After features/support/hooks.rb:330 1.657
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
6:44.360
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 with a persistent partition enabled and logged in 11.944
And no SquashFS delta is installed 0.100
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.525
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.302
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.480
When the network is plugged 0.069
And Tor is ready 25.472
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.370
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.115
Given I shutdown Tails and wait for the computer to power off 10.902
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.258
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.299
And the file system changes introduced in version 6.2~testoverlayfs are present 0.372
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# 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.393
When the network is plugged 0.062
And Tor is ready 20.191
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.085
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.969
Given I shutdown Tails and wait for the computer to power off 4.451
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.739
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 1.924
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.068
# 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.348
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.328
When the network is plugged 0.071
And Tor is ready 19.848
Then the Upgrader considers the system as up-to-date 0.326
# 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.204
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.190
After features/support/hooks.rb:330 0.794
After features/support/hooks.rb:100 0.034
Tags: @product @automatic_upgrade
39.819
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.034
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.789
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.087
And the signing key used by the Upgrader is outdated 0.127
But a current signing key is available on our website 0.000
When the network is plugged 0.139
And Tor is ready 20.671
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.968
After features/support/hooks.rb:330 0.900
After features/support/hooks.rb:100 0.000