Project Number Date
test_Tails_ISO_stable 5132 02 Oct 2024, 08:34

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:15.740 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
1:58.999
Before features/support/hooks.rb:269 0.004
Given a computer 0.200
And I create a 7200 MiB disk named "old" 0.063
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 28.942
When I start Tails from USB drive "old" with network unplugged 1:24.370
Then the boot device has safe access rights 3.257
And Tails is running from USB drive "old" 0.343
And there is no persistence partition on USB drive "old" 0.081
And process "udev-watchdog" is running 0.116
And udev-watchdog is monitoring the correct device 0.352
And I unplug USB drive "old" 0.212
After features/support/hooks.rb:326 3.585
After features/support/hooks.rb:100 0.010
Tags: @product
2:7.203
Before features/support/hooks.rb:269 0.004
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login 1:23.286
Then Tails is running from USB drive "old" 0.318
And I create a persistent partition 32.388
And I take note of which tps features are available 1.656
Then a Tails persistence partition exists on USB drive "old" 0.782
And I shutdown Tails and wait for the computer to power off 8.582
After features/support/hooks.rb:326 0.223
After features/support/hooks.rb:100 0.008
Tags: @product
2:50.406
Before features/support/hooks.rb:269 0.005
Given a computer 0.217
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.251
Then Tails is running from USB drive "old" 0.428
And all tps features are active 2.091
When I write some files expected to persist 1.857
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.239
And all persistence configuration files have safe access rights 0.406
And all persistent directories from the old Tails version have safe access rights 3.334
And I take note of which tps features are available 0.473
And I shutdown Tails and wait for the computer to power off 4.576
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.529
After features/support/hooks.rb:326 0.142
After features/support/hooks.rb:100 0.009
Tags: @product
2:31.831
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.656
And I log in to a new session 18.319
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.578
And I plug USB drive "to_upgrade" 2.423
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.678
Then the running Tails is installed on USB drive "to_upgrade" 21.735
And I unplug USB drive "to_upgrade" 0.240
And I unplug USB drive "__internal" 0.200
After features/support/hooks.rb:326 2.277
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.969
Before features/support/hooks.rb:269 0.008
Given a computer 0.208
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.573
Then all tps features from the old Tails version are active 2.062
And Tails is running from USB drive "to_upgrade" 0.325
And the boot device has safe access rights 3.442
And the expected persistent files created with the old Tails version are present in the filesystem 1.571
And all persistent directories from the old Tails version have safe access rights 2.784
After features/support/hooks.rb:326 1.083
After features/support/hooks.rb:100 0.027
Tags: @product @automatic_upgrade
6:48.643
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.883
And no SquashFS delta is installed 0.158
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.766
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.324
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.449
When the network is plugged 0.084
And Tor is ready 21.697
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.624
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.953
Given I shutdown Tails and wait for the computer to power off 8.690
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.813
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 3.371
And the file system changes introduced in version 6.2~testoverlayfs are present 0.313
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.299
# 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.312
When the network is plugged 0.101
And Tor is ready 18.606
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.255
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.970
Given I shutdown Tails and wait for the computer to power off 4.378
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.328
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.407
And the file system changes introduced in version 6.3~testoverlayfs are present 0.457
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.395
When the network is plugged 0.083
And Tor is ready 18.753
Then the Upgrader considers the system as up-to-date 10.816
# 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.840
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.984
After features/support/hooks.rb:326 0.762
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
36.685
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 10.215
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.441
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.848
But a current signing key is available on our website 0.000
When the network is plugged 0.071
And Tor is ready 18.744
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.309
After features/support/hooks.rb:326 1.012
After features/support/hooks.rb:100 0.000