Project Number Date
test_Tails_ISO_devel 3670 29 Jan 2025, 14:43

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:16.765 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:24.309
Before features/support/hooks.rb:269 0.004
Given a computer 0.201
And I create a 7200 MiB disk named "old" 0.080
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 31.864
When I start Tails from USB drive "old" with network unplugged 1:46.318
Then the boot device has safe access rights 3.500
And Tails is running from USB drive "old" 0.447
And there is no persistence partition on USB drive "old" 0.081
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.400
And I unplug USB drive "old" 0.256
After features/support/hooks.rb:326 3.813
After features/support/hooks.rb:100 0.009
Tags: @product
2:6.885
Before features/support/hooks.rb:269 0.004
Given a computer 0.259
And I start Tails from USB drive "old" with network unplugged and I login 1:25.660
Then Tails is running from USB drive "old" 0.390
And I create a persistent partition 31.963
And I take note of which tps features are available 1.446
Then a Tails persistence partition exists on USB drive "old" 0.877
And I shutdown Tails and wait for the computer to power off 6.286
After features/support/hooks.rb:326 0.168
After features/support/hooks.rb:100 0.006
Tags: @product
2:53.869
Before features/support/hooks.rb:269 0.003
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.025
Then Tails is running from USB drive "old" 0.465
And all tps features are active 4.270
When I write some files expected to persist 1.901
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.262
And all persistence configuration files have safe access rights 0.474
And all persistent directories from the old Tails version have safe access rights 2.379
And I take note of which tps features are available 1.711
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" 24.866
After features/support/hooks.rb:326 0.129
After features/support/hooks.rb:100 0.006
Tags: @product
2:27.360
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.566
And I log in to a new session 18.284
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.311
And I plug USB drive "to_upgrade" 2.380
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.941
Then the running Tails is installed on USB drive "to_upgrade" 17.415
And I unplug USB drive "to_upgrade" 0.239
And I unplug USB drive "__internal" 0.221
After features/support/hooks.rb:326 6.750
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.775
Before features/support/hooks.rb:269 0.005
Given a computer 0.202
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.052
Then all tps features from the old Tails version are active 1.742
And Tails is running from USB drive "to_upgrade" 0.338
And the boot device has safe access rights 3.244
And the expected persistent files created with the old Tails version are present in the filesystem 1.649
And all persistent directories from the old Tails version have safe access rights 2.544
After features/support/hooks.rb:326 0.702
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
6:33.622
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 14.155
And no SquashFS delta is installed 0.091
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.448
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.317
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.466
When the network is plugged 0.086
And Tor is ready 19.621
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.658
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.529
Given I shutdown Tails and wait for the computer to power off 8.526
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.142
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.249
And the file system changes introduced in version 6.2~testoverlayfs are present 0.336
And only the 6.2~testoverlayfs SquashFS delta is installed 0.081
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.356
# 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.444
When the network is plugged 0.088
And Tor is ready 19.676
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.249
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.762
Given I shutdown Tails and wait for the computer to power off 4.324
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.626
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 3.829
And the file system changes introduced in version 6.3~testoverlayfs are present 0.590
And only the 6.3~testoverlayfs SquashFS delta is installed 0.098
# 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.455
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.296
When the network is plugged 0.068
And Tor is ready 17.934
Then the Upgrader considers the system as up-to-date 0.319
# 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.858
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.831
After features/support/hooks.rb:326 0.753
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
36.942
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 9.920
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.392
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 0.079
But a current signing key is available on our website 0.000
When the network is plugged 0.075
And Tor is ready 21.319
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.089
After features/support/hooks.rb:326 0.710
After features/support/hooks.rb:100 0.000