Project Number Date
test_Tails_ISO_stable 4923 09 Jul 2024, 13:53

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:18.519 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:46.182
Before features/support/hooks.rb:269 0.004
Given a computer 0.188
And I create a 7200 MiB disk named "old" 0.038
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 31.799
When I start Tails from USB drive "old" with network unplugged 2:9.088
Then the boot device has safe access rights 3.033
And Tails is running from USB drive "old" 0.329
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.298
And I unplug USB drive "old" 0.194
After features/support/hooks.rb:326 7.568
After features/support/hooks.rb:100 0.008
Tags: @product
2:5.851
Before features/support/hooks.rb:269 0.005
Given a computer 0.215
And I start Tails from USB drive "old" with network unplugged and I login 1:23.147
Then Tails is running from USB drive "old" 0.360
And I create a persistent partition 31.512
And I take note of which tps features are available 1.400
Then a Tails persistence partition exists on USB drive "old" 0.951
And I shutdown Tails and wait for the computer to power off 8.262
After features/support/hooks.rb:326 0.140
After features/support/hooks.rb:100 0.011
Tags: @product
2:51.691
Before features/support/hooks.rb:269 0.007
Given a computer 0.215
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.122
Then Tails is running from USB drive "old" 0.329
And all tps features are active 1.992
When I write some files expected to persist 2.004
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.276
And all persistence configuration files have safe access rights 0.392
And all persistent directories from the old Tails version have safe access rights 2.548
And I take note of which tps features are available 0.399
And I shutdown Tails and wait for the computer to power off 4.409
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.000
After features/support/hooks.rb:326 0.103
After features/support/hooks.rb:100 0.008
Tags: @product
2:23.651
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.000
And I log in to a new session 17.826
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.590
And I plug USB drive "to_upgrade" 2.456
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.152
Then the running Tails is installed on USB drive "to_upgrade" 18.207
And I unplug USB drive "to_upgrade" 0.219
And I unplug USB drive "__internal" 0.198
After features/support/hooks.rb:326 3.655
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.075
Before features/support/hooks.rb:269 0.007
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.855
Then all tps features from the old Tails version are active 1.587
And Tails is running from USB drive "to_upgrade" 0.325
And the boot device has safe access rights 3.435
And the expected persistent files created with the old Tails version are present in the filesystem 1.431
And all persistent directories from the old Tails version have safe access rights 2.224
After features/support/hooks.rb:326 0.912
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
6:19.539
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 11.483
And no SquashFS delta is installed 0.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.252
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.279
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.409
When the network is plugged 0.037
And Tor is ready 20.180
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.229
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.863
Given I shutdown Tails and wait for the computer to power off 8.805
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.458
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.091
And the file system changes introduced in version 6.2~testoverlayfs are present 0.283
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.332
# 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.311
When the network is plugged 0.032
And Tor is ready 19.899
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.893
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.561
Given I shutdown Tails and wait for the computer to power off 4.481
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.901
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.885
And the file system changes introduced in version 6.3~testoverlayfs are present 0.522
And only the 6.3~testoverlayfs SquashFS delta is installed 0.086
# 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.445
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.284
When the network is plugged 0.036
And Tor is ready 20.128
Then the Upgrader considers the system as up-to-date 0.305
# 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.977
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.866
After features/support/hooks.rb:326 0.762
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
34.526
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.739
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.356
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the signing key used by the Upgrader is outdated 0.776
But a current signing key is available on our website 0.000
When the network is plugged 0.040
And Tor is ready 18.363
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.187
After features/support/hooks.rb:326 0.676
After features/support/hooks.rb:100 0.000