Project Number Date
test_Tails_ISO_stable 5130 01 Oct 2024, 12:40

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:59.427 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:32.321
Before features/support/hooks.rb:269 0.005
Given a computer 0.201
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 29.956
When I start Tails from USB drive "old" with network unplugged 1:56.846
Then the boot device has safe access rights 3.116
And Tails is running from USB drive "old" 0.325
And there is no persistence partition on USB drive "old" 0.089
And process "udev-watchdog" is running 0.113
And udev-watchdog is monitoring the correct device 0.373
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:326 7.251
After features/support/hooks.rb:100 0.009
Tags: @product
2:21.476
Before features/support/hooks.rb:269 0.006
Given a computer 0.225
And I start Tails from USB drive "old" with network unplugged and I login 1:35.123
Then Tails is running from USB drive "old" 0.322
And I create a persistent partition 34.768
And I take note of which tps features are available 1.517
Then a Tails persistence partition exists on USB drive "old" 0.893
And I shutdown Tails and wait for the computer to power off 8.626
After features/support/hooks.rb:326 0.174
After features/support/hooks.rb:100 0.012
Tags: @product
2:57.142
Before features/support/hooks.rb:269 0.008
Given a computer 0.215
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.897
Then Tails is running from USB drive "old" 0.479
And all tps features are active 3.222
When I write some files expected to persist 1.722
# 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.381
And all persistent directories from the old Tails version have safe access rights 2.737
And I take note of which tps features are available 0.802
And I shutdown Tails and wait for the computer to power off 4.560
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.913
After features/support/hooks.rb:326 0.139
After features/support/hooks.rb:100 0.010
Tags: @product
2:37.779
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.838
And I log in to a new session 20.569
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.707
And I plug USB drive "to_upgrade" 2.564
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.926
Then the running Tails is installed on USB drive "to_upgrade" 27.646
And I unplug USB drive "to_upgrade" 0.247
And I unplug USB drive "__internal" 0.279
After features/support/hooks.rb:326 7.262
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.805
Before features/support/hooks.rb:269 0.006
Given a computer 0.216
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.100
Then all tps features from the old Tails version are active 1.681
And Tails is running from USB drive "to_upgrade" 0.327
And the boot device has safe access rights 3.581
And the expected persistent files created with the old Tails version are present in the filesystem 1.473
And all persistent directories from the old Tails version have safe access rights 2.423
After features/support/hooks.rb:326 0.706
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:33.016
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.332
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.594
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.278
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.520
When the network is plugged 0.066
And Tor is ready 24.701
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.904
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.820
Given I shutdown Tails and wait for the computer to power off 16.714
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.735
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.603
And the file system changes introduced in version 6.2~testoverlayfs are present 0.349
And only the 6.2~testoverlayfs SquashFS delta is installed 0.094
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.335
# 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.323
When the network is plugged 0.098
And Tor is ready 18.719
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.879
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.249
Given I shutdown Tails and wait for the computer to power off 6.433
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.967
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.161
And the file system changes introduced in version 6.3~testoverlayfs are present 0.446
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.310
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.294
When the network is plugged 0.125
And Tor is ready 19.134
Then the Upgrader considers the system as up-to-date 0.307
# 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.124
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.136
After features/support/hooks.rb:326 0.746
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
40.885
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 10.402
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.297
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 1.000
But a current signing key is available on our website 0.000
When the network is plugged 0.088
And Tor is ready 23.918
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.119
After features/support/hooks.rb:326 0.904
After features/support/hooks.rb:100 0.000