Project Number Date
test_Tails_ISO_stable 5138 03 Oct 2024, 19:10

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:54.803 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:18.673
Before features/support/hooks.rb:269 0.004
Given a computer 0.291
And I create a 7200 MiB disk named "old" 0.328
And I plug USB drive "old" 1.147
And I write an old version of the Tails USB image to disk "old" 32.969
When I start Tails from USB drive "old" with network unplugged 1:39.356
Then the boot device has safe access rights 3.504
And Tails is running from USB drive "old" 0.394
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.325
And I unplug USB drive "old" 0.195
After features/support/hooks.rb:326 3.616
After features/support/hooks.rb:100 0.011
Tags: @product
2:18.338
Before features/support/hooks.rb:269 0.005
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login 1:32.475
Then Tails is running from USB drive "old" 0.437
And I create a persistent partition 33.754
And I take note of which tps features are available 1.937
Then a Tails persistence partition exists on USB drive "old" 0.872
And I shutdown Tails and wait for the computer to power off 8.661
After features/support/hooks.rb:326 0.169
After features/support/hooks.rb:100 0.007
Tags: @product
3:4.516
Before features/support/hooks.rb:269 0.003
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:26.526
Then Tails is running from USB drive "old" 0.316
And all tps features are active 2.491
When I write some files expected to persist 1.904
# 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.466
And all persistent directories from the old Tails version have safe access rights 2.616
And I take note of which tps features are available 0.501
And I shutdown Tails and wait for the computer to power off 4.364
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.922
After features/support/hooks.rb:326 0.161
After features/support/hooks.rb:100 0.007
Tags: @product
2:31.247
Before features/support/hooks.rb:269 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 10.197
And I log in to a new session 20.069
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.894
And I plug USB drive "to_upgrade" 2.441
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.908
Then the running Tails is installed on USB drive "to_upgrade" 19.266
And I unplug USB drive "to_upgrade" 0.264
And I unplug USB drive "__internal" 0.204
After features/support/hooks.rb:326 5.634
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.142
Before features/support/hooks.rb:269 0.005
Given a computer 0.283
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.525
Then all tps features from the old Tails version are active 1.729
And Tails is running from USB drive "to_upgrade" 0.361
And the boot device has safe access rights 3.375
And the expected persistent files created with the old Tails version are present in the filesystem 1.416
And all persistent directories from the old Tails version have safe access rights 2.451
After features/support/hooks.rb:326 0.672
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:51.832
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.694
And no SquashFS delta is installed 0.088
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.390
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.131
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.360
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.443
When the network is plugged 0.066
And Tor is ready 21.083
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.620
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.985
Given I shutdown Tails and wait for the computer to power off 1:23.707
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.233
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.330
And the file system changes introduced in version 6.2~testoverlayfs are present 0.299
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.338
# 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.518
When the network is plugged 0.102
And Tor is ready 17.618
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.353
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.111
Given I shutdown Tails and wait for the computer to power off 4.305
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.329
Then Tails is running version 6.3~testoverlayfs 0.024
And all tps features are active 2.048
And the file system changes introduced in version 6.3~testoverlayfs are present 0.549
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.298
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.311
When the network is plugged 0.094
And Tor is ready 21.503
Then the Upgrader considers the system as up-to-date 0.328
# 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.322
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.073
After features/support/hooks.rb:326 0.790
After features/support/hooks.rb:100 0.058
Tags: @product @automatic_upgrade
37.050
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 10.262
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.301
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.945
But a current signing key is available on our website 0.000
When the network is plugged 0.103
And Tor is ready 18.467
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.908
After features/support/hooks.rb:326 0.826
After features/support/hooks.rb:100 0.000