Project Number Date
test_Tails_ISO_stable 5047 26 Aug 2024, 15:59

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:9.134 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:8.862
Before features/support/hooks.rb:269 0.004
Given a computer 0.190
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 30.055
When I start Tails from USB drive "old" with network unplugged 1:33.615
Then the boot device has safe access rights 2.906
And Tails is running from USB drive "old" 0.355
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.309
And I unplug USB drive "old" 0.178
After features/support/hooks.rb:326 7.224
After features/support/hooks.rb:100 0.009
Tags: @product
2:5.216
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.324
Then Tails is running from USB drive "old" 0.301
And I create a persistent partition 31.926
And I take note of which tps features are available 1.418
Then a Tails persistence partition exists on USB drive "old" 0.846
And I shutdown Tails and wait for the computer to power off 8.206
After features/support/hooks.rb:326 0.171
After features/support/hooks.rb:100 0.009
Tags: @product
2:46.428
Before features/support/hooks.rb:269 0.006
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:9.954
Then Tails is running from USB drive "old" 0.335
And all tps features are active 2.048
When I write some files expected to persist 1.782
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.240
And all persistence configuration files have safe access rights 0.376
And all persistent directories from the old Tails version have safe access rights 2.510
And I take note of which tps features are available 0.454
And I shutdown Tails and wait for the computer to power off 4.262
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.275
After features/support/hooks.rb:326 0.097
After features/support/hooks.rb:100 0.009
Tags: @product
2:27.037
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.125
And I log in to a new session 20.132
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.445
And I plug USB drive "to_upgrade" 2.446
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.673
Then the running Tails is installed on USB drive "to_upgrade" 18.805
And I unplug USB drive "to_upgrade" 0.205
And I unplug USB drive "__internal" 0.202
After features/support/hooks.rb:326 2.949
After features/support/hooks.rb:100 0.000
Tags: @product
2:7.735
Before features/support/hooks.rb:269 0.006
Given a computer 0.177
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:58.367
Then all tps features from the old Tails version are active 1.709
And Tails is running from USB drive "to_upgrade" 0.322
And the boot device has safe access rights 3.187
And the expected persistent files created with the old Tails version are present in the filesystem 1.522
And all persistent directories from the old Tails version have safe access rights 2.446
After features/support/hooks.rb:326 0.729
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:0.819
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.290
And no SquashFS delta is installed 0.181
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.293
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.303
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.423
When the network is plugged 0.089
And Tor is ready 22.969
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.925
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.313
Given I shutdown Tails and wait for the computer to power off 14.943
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.608
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.208
And the file system changes introduced in version 6.2~testoverlayfs are present 0.290
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.308
# 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.380
When the network is plugged 0.073
And Tor is ready 20.841
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.863
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.732
Given I shutdown Tails and wait for the computer to power off 4.641
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.594
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.011
And the file system changes introduced in version 6.3~testoverlayfs are present 0.425
And only the 6.3~testoverlayfs SquashFS delta is installed 0.061
# 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.324
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.265
When the network is plugged 0.075
And Tor is ready 47.206
Then the Upgrader considers the system as up-to-date 0.341
# 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 13.541
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.135
After features/support/hooks.rb:326 0.723
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
33.035
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 9.958
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.264
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the signing key used by the Upgrader is outdated 0.766
But a current signing key is available on our website 0.000
When the network is plugged 0.069
And Tor is ready 15.295
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.608
After features/support/hooks.rb:326 0.948
After features/support/hooks.rb:100 0.000