Project Number Date
test_Tails_ISO_stable 5308 02 Dec 2024, 12:33

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:20.020 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:23.257
Before features/support/hooks.rb:269 0.006
Given a computer 0.194
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.064
And I write an old version of the Tails USB image to disk "old" 31.539
When I start Tails from USB drive "old" with network unplugged 1:46.064
Then the boot device has safe access rights 3.261
And Tails is running from USB drive "old" 0.358
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.342
And I unplug USB drive "old" 0.219
After features/support/hooks.rb:326 3.714
After features/support/hooks.rb:100 0.008
Tags: @product
2:21.705
Before features/support/hooks.rb:269 0.007
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login 1:37.349
Then Tails is running from USB drive "old" 0.344
And I create a persistent partition 32.700
And I take note of which tps features are available 1.509
Then a Tails persistence partition exists on USB drive "old" 0.914
And I shutdown Tails and wait for the computer to power off 8.688
After features/support/hooks.rb:326 0.200
After features/support/hooks.rb:100 0.010
Tags: @product
2:53.011
Before features/support/hooks.rb:269 0.005
Given a computer 0.223
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.794
Then Tails is running from USB drive "old" 0.686
And all tps features are active 2.205
When I write some files expected to persist 1.957
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.299
And all persistence configuration files have safe access rights 0.412
And all persistent directories from the old Tails version have safe access rights 2.782
And I take note of which tps features are available 0.486
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" 25.602
After features/support/hooks.rb:326 0.162
After features/support/hooks.rb:100 0.012
Tags: @product
2:39.709
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.991
And I log in to a new session 23.181
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.931
And I plug USB drive "to_upgrade" 2.468
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.288
Then the running Tails is installed on USB drive "to_upgrade" 22.354
And I unplug USB drive "to_upgrade" 0.205
And I unplug USB drive "__internal" 0.287
After features/support/hooks.rb:326 0.960
After features/support/hooks.rb:100 0.000
Tags: @product
2:27.486
Before features/support/hooks.rb:269 0.007
Given a computer 0.235
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:17.600
Then all tps features from the old Tails version are active 1.803
And Tails is running from USB drive "to_upgrade" 0.382
And the boot device has safe access rights 3.488
And the expected persistent files created with the old Tails version are present in the filesystem 1.507
And all persistent directories from the old Tails version have safe access rights 2.467
After features/support/hooks.rb:326 0.666
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
6:56.459
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 15.453
And no SquashFS delta is installed 2.160
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.451
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.292
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.493
When the network is plugged 0.071
And Tor is ready 21.312
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.706
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.232
Given I shutdown Tails and wait for the computer to power off 8.777
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.522
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.384
And the file system changes introduced in version 6.2~testoverlayfs are present 0.312
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.410
# 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.286
When the network is plugged 0.099
And Tor is ready 21.451
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.856
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.303
Given I shutdown Tails and wait for the computer to power off 4.455
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.041
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.090
And the file system changes introduced in version 6.3~testoverlayfs are present 0.527
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.289
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.321
When the network is plugged 0.074
And Tor is ready 20.870
Then the Upgrader considers the system as up-to-date 0.362
# 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 15.980
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.603
After features/support/hooks.rb:326 0.932
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
38.390
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 10.527
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.418
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the signing key used by the Upgrader is outdated 0.844
But a current signing key is available on our website 0.000
When the network is plugged 0.117
And Tor is ready 19.134
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.282
After features/support/hooks.rb:326 0.726
After features/support/hooks.rb:100 0.000