Project Number Date
test_Tails_ISO_devel 3631 03 Jan 2025, 12:25

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:5.306 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
1:57.418
Before features/support/hooks.rb:269 0.006
Given a computer 0.195
And I create a 7200 MiB disk named "old" 0.069
And I plug USB drive "old" 1.077
And I write an old version of the Tails USB image to disk "old" 31.398
When I start Tails from USB drive "old" with network unplugged 1:20.927
Then the boot device has safe access rights 2.800
And Tails is running from USB drive "old" 0.302
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.088
And udev-watchdog is monitoring the correct device 0.290
And I unplug USB drive "old" 0.191
After features/support/hooks.rb:326 8.375
After features/support/hooks.rb:100 0.009
Tags: @product
2:5.536
Before features/support/hooks.rb:269 0.005
Given a computer 0.193
And I start Tails from USB drive "old" with network unplugged and I login 1:22.929
Then Tails is running from USB drive "old" 0.322
And I create a persistent partition 31.293
And I take note of which tps features are available 1.567
Then a Tails persistence partition exists on USB drive "old" 0.819
And I shutdown Tails and wait for the computer to power off 8.409
After features/support/hooks.rb:326 0.203
After features/support/hooks.rb:100 0.011
Tags: @product
3:0.007
Before features/support/hooks.rb:269 0.008
Given a computer 0.219
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.520
Then Tails is running from USB drive "old" 0.323
And all tps features are active 2.140
When I write some files expected to persist 1.817
# 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.373
And all persistent directories from the old Tails version have safe access rights 2.393
And I take note of which tps features are available 0.442
And I shutdown Tails and wait for the computer to power off 4.136
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.430
After features/support/hooks.rb:326 0.125
After features/support/hooks.rb:100 0.008
Tags: @product
2:31.971
Before features/support/hooks.rb:269 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.031
And I log in to a new session 17.914
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.528
And I plug USB drive "to_upgrade" 2.383
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.675
Then the running Tails is installed on USB drive "to_upgrade" 24.056
And I unplug USB drive "to_upgrade" 0.189
And I unplug USB drive "__internal" 0.190
After features/support/hooks.rb:326 3.495
After features/support/hooks.rb:100 0.000
Tags: @product
2:9.489
Before features/support/hooks.rb:269 0.006
Given a computer 0.193
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:0.288
Then all tps features from the old Tails version are active 1.642
And Tails is running from USB drive "to_upgrade" 0.371
And the boot device has safe access rights 3.191
And the expected persistent files created with the old Tails version are present in the filesystem 1.446
And all persistent directories from the old Tails version have safe access rights 2.356
After features/support/hooks.rb:326 0.847
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:44.284
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.443
And no SquashFS delta is installed 0.149
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.832
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.122
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.394
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.504
When the network is plugged 0.233
And Tor is ready 20.206
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.907
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.258
Given I shutdown Tails and wait for the computer to power off 10.652
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.269
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.360
And the file system changes introduced in version 6.2~testoverlayfs are present 0.285
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.294
# 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.277
When the network is plugged 0.067
And Tor is ready 18.464
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.010
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.590
Given I shutdown Tails and wait for the computer to power off 4.349
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.807
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.041
And the file system changes introduced in version 6.3~testoverlayfs are present 0.441
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.362
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.287
When the network is plugged 0.082
And Tor is ready 19.691
Then the Upgrader considers the system as up-to-date 10.806
# 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.973
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.951
After features/support/hooks.rb:326 0.801
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
36.598
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.614
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.394
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.107
And the signing key used by the Upgrader is outdated 0.975
But a current signing key is available on our website 0.000
When the network is plugged 0.111
And Tor is ready 20.320
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.073
After features/support/hooks.rb:326 0.671
After features/support/hooks.rb:100 0.000