Project Number Date
test_Tails_ISO_stable 4901 18 Jun 2024, 20:25

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 21:53.736 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
3:16.452
Before features/support/hooks.rb:269 0.005
Given a computer 0.283
And I create a 7200 MiB disk named "old" 0.069
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 1:5.330
When I start Tails from USB drive "old" with network unplugged 2:5.266
Then the boot device has safe access rights 3.369
And Tails is running from USB drive "old" 0.385
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.089
And udev-watchdog is monitoring the correct device 0.328
And I unplug USB drive "old" 0.209
After features/support/hooks.rb:326 7.005
After features/support/hooks.rb:100 0.009
Tags: @product
2:17.131
Before features/support/hooks.rb:269 0.005
Given a computer 0.296
And I start Tails from USB drive "old" with network unplugged and I login 1:28.313
Then Tails is running from USB drive "old" 0.369
And I create a persistent partition 35.366
And I take note of which tps features are available 3.490
Then a Tails persistence partition exists on USB drive "old" 0.869
And I shutdown Tails and wait for the computer to power off 8.423
After features/support/hooks.rb:326 0.191
After features/support/hooks.rb:100 0.009
Tags: @product
3:20.545
Before features/support/hooks.rb:269 0.006
Given a computer 0.845
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:29.428
Then Tails is running from USB drive "old" 0.377
And all tps features are active 7.143
When I write some files expected to persist 1.848
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.269
And all persistence configuration files have safe access rights 0.480
And all persistent directories from the old Tails version have safe access rights 2.810
And I take note of which tps features are available 0.699
And I shutdown Tails and wait for the computer to power off 8.488
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 28.153
After features/support/hooks.rb:326 0.147
After features/support/hooks.rb:100 0.009
Tags: @product
2:42.443
Before features/support/hooks.rb:269 0.010
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 18.604
And I log in to a new session 18.797
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.982
And I plug USB drive "to_upgrade" 2.512
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.513
Then the running Tails is installed on USB drive "to_upgrade" 20.500
And I unplug USB drive "to_upgrade" 0.272
And I unplug USB drive "__internal" 0.260
After features/support/hooks.rb:326 3.866
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.388
Before features/support/hooks.rb:269 0.009
Given a computer 0.442
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.538
Then all tps features from the old Tails version are active 1.991
And Tails is running from USB drive "to_upgrade" 0.344
And the boot device has safe access rights 3.574
And the expected persistent files created with the old Tails version are present in the filesystem 1.723
And all persistent directories from the old Tails version have safe access rights 2.773
After features/support/hooks.rb:326 0.634
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
7:16.878
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 22.776
And no SquashFS delta is installed 0.161
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.357
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.088
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.358
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.783
When the network is plugged 0.064
And Tor is ready 50.831
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.701
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.055
Given I shutdown Tails and wait for the computer to power off 8.968
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.722
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.907
And the file system changes introduced in version 6.2~testoverlayfs are present 0.345
And only the 6.2~testoverlayfs SquashFS delta is installed 0.092
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.362
# 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.300
When the network is plugged 0.106
And Tor is ready 18.132
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.030
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.116
Given I shutdown Tails and wait for the computer to power off 7.070
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.663
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.360
And the file system changes introduced in version 6.3~testoverlayfs are present 0.633
And only the 6.3~testoverlayfs SquashFS delta is installed 0.101
# 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.585
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.417
When the network is plugged 0.078
And Tor is ready 19.754
Then the Upgrader considers the system as up-to-date 0.324
# 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.473
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.115
After features/support/hooks.rb:326 0.784
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
39.897
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.422
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.363
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.076
And the signing key used by the Upgrader is outdated 0.839
But a current signing key is available on our website 0.000
When the network is plugged 0.042
And Tor is ready 22.530
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.622
After features/support/hooks.rb:326 0.943
After features/support/hooks.rb:100 0.000