Project Number Date
test_Tails_ISO_devel 3462 14 Jul 2024, 12:31

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 18:38.488 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.532
Before features/support/hooks.rb:269 0.006
Given a computer 0.202
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.068
And I write an old version of the Tails USB image to disk "old" 29.935
When I start Tails from USB drive "old" with network unplugged 1:48.081
Then the boot device has safe access rights 2.889
And Tails is running from USB drive "old" 0.597
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.123
And udev-watchdog is monitoring the correct device 0.332
And I unplug USB drive "old" 0.183
After features/support/hooks.rb:326 7.926
After features/support/hooks.rb:100 0.009
Tags: @product
2:1.337
Before features/support/hooks.rb:269 0.006
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login 1:21.400
Then Tails is running from USB drive "old" 0.317
And I create a persistent partition 31.039
And I take note of which tps features are available 1.409
Then a Tails persistence partition exists on USB drive "old" 0.813
And I shutdown Tails and wait for the computer to power off 6.161
After features/support/hooks.rb:326 0.168
After features/support/hooks.rb:100 0.009
Tags: @product
2:42.720
Before features/support/hooks.rb:269 0.006
Given a computer 0.175
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:6.260
Then Tails is running from USB drive "old" 0.361
And all tps features are active 1.938
When I write some files expected to persist 1.742
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.221
And all persistence configuration files have safe access rights 0.519
And all persistent directories from the old Tails version have safe access rights 2.698
And I take note of which tps features are available 0.442
And I shutdown Tails and wait for the computer to power off 4.407
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.952
After features/support/hooks.rb:326 0.139
After features/support/hooks.rb:100 0.010
Tags: @product
2:34.862
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 23.893
And I log in to a new session 18.288
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.424
And I plug USB drive "to_upgrade" 2.364
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.728
Then the running Tails is installed on USB drive "to_upgrade" 16.650
And I unplug USB drive "to_upgrade" 0.279
And I unplug USB drive "__internal" 0.232
After features/support/hooks.rb:326 3.639
After features/support/hooks.rb:100 0.000
Tags: @product
2:8.928
Before features/support/hooks.rb:269 0.005
Given a computer 0.201
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:59.616
Then all tps features from the old Tails version are active 1.692
And Tails is running from USB drive "to_upgrade" 0.380
And the boot device has safe access rights 3.250
And the expected persistent files created with the old Tails version are present in the filesystem 1.491
And all persistent directories from the old Tails version have safe access rights 2.296
After features/support/hooks.rb:326 1.212
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:15.374
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 11.806
And no SquashFS delta is installed 0.090
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.292
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.290
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.397
When the network is plugged 0.049
And Tor is ready 24.423
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.040
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.290
Given I shutdown Tails and wait for the computer to power off 11.003
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.454
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.247
And the file system changes introduced in version 6.2~testoverlayfs are present 0.302
And only the 6.2~testoverlayfs SquashFS delta is installed 0.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.431
# 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.314
When the network is plugged 0.066
And Tor is ready 18.505
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.848
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.941
Given I shutdown Tails and wait for the computer to power off 4.428
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.631
Then Tails is running version 6.3~testoverlayfs 0.021
And all tps features are active 2.189
And the file system changes introduced in version 6.3~testoverlayfs are present 0.541
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.340
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.310
When the network is plugged 0.065
And Tor is ready 18.277
Then the Upgrader considers the system as up-to-date 0.356
# 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.003
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.197
After features/support/hooks.rb:326 0.733
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
31.732
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 9.545
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.309
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the signing key used by the Upgrader is outdated 0.737
But a current signing key is available on our website 0.000
When the network is plugged 0.178
And Tor is ready 15.983
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.905
After features/support/hooks.rb:326 0.606
After features/support/hooks.rb:100 0.000