Project Number Date
test_Tails_ISO_devel 3643 10 Jan 2025, 17:52

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:6.307 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:0.806
Before features/support/hooks.rb:269 0.003
Given a computer 0.177
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 29.696
When I start Tails from USB drive "old" with network unplugged 1:25.915
Then the boot device has safe access rights 2.851
And Tails is running from USB drive "old" 0.336
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.334
And I unplug USB drive "old" 0.222
After features/support/hooks.rb:326 3.804
After features/support/hooks.rb:100 0.008
Tags: @product
2:8.612
Before features/support/hooks.rb:269 0.004
Given a computer 1.012
And I start Tails from USB drive "old" with network unplugged and I login 1:24.198
Then Tails is running from USB drive "old" 0.319
And I create a persistent partition 32.465
And I take note of which tps features are available 1.398
Then a Tails persistence partition exists on USB drive "old" 0.894
And I shutdown Tails and wait for the computer to power off 8.322
After features/support/hooks.rb:326 0.160
After features/support/hooks.rb:100 0.005
Tags: @product
2:47.732
Before features/support/hooks.rb:269 0.003
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.408
Then Tails is running from USB drive "old" 1.300
And all tps features are active 2.108
When I write some files expected to persist 1.773
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.268
And all persistence configuration files have safe access rights 0.555
And all persistent directories from the old Tails version have safe access rights 2.418
And I take note of which tps features are available 0.415
And I shutdown Tails and wait for the computer to power off 4.514
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 22.784
After features/support/hooks.rb:326 0.125
After features/support/hooks.rb:100 0.014
Tags: @product
2:27.846
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.004
And I log in to a new session 19.215
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.466
And I plug USB drive "to_upgrade" 2.375
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.210
Then the running Tails is installed on USB drive "to_upgrade" 18.147
And I unplug USB drive "to_upgrade" 0.201
And I unplug USB drive "__internal" 0.225
After features/support/hooks.rb:326 2.761
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.663
Before features/support/hooks.rb:269 0.003
Given a computer 0.165
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.133
Then all tps features from the old Tails version are active 1.733
And Tails is running from USB drive "to_upgrade" 0.290
And the boot device has safe access rights 3.530
And the expected persistent files created with the old Tails version are present in the filesystem 1.403
And all persistent directories from the old Tails version have safe access rights 2.407
After features/support/hooks.rb:326 0.685
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
7:41.580
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.906
And no SquashFS delta is installed 0.751
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.262
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.274
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.442
When the network is plugged 0.064
And Tor is ready 24.084
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.207
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.233
Given I shutdown Tails and wait for the computer to power off 1:14.262
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.882
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 2.203
And the file system changes introduced in version 6.2~testoverlayfs are present 0.346
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.413
# 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.532
When the network is plugged 0.088
And Tor is ready 19.203
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.070
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.218
Given I shutdown Tails and wait for the computer to power off 4.299
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.383
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.068
And the file system changes introduced in version 6.3~testoverlayfs are present 0.648
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.308
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.296
When the network is plugged 0.089
And Tor is ready 20.336
Then the Upgrader considers the system as up-to-date 0.353
# 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.118
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.982
After features/support/hooks.rb:326 0.773
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
39.066
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.039
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.509
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.063
But a current signing key is available on our website 0.000
When the network is plugged 0.081
And Tor is ready 20.658
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.661
After features/support/hooks.rb:326 0.745
After features/support/hooks.rb:100 0.000