Project Number Date
test_Tails_ISO_stable 5198 19 Oct 2024, 08:52

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:26.246 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:19.219
Before features/support/hooks.rb:269 0.005
Given a computer 0.221
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 33.175
When I start Tails from USB drive "old" with network unplugged 1:40.299
Then the boot device has safe access rights 3.327
And Tails is running from USB drive "old" 0.369
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.107
And udev-watchdog is monitoring the correct device 0.341
And I unplug USB drive "old" 0.201
After features/support/hooks.rb:326 3.511
After features/support/hooks.rb:100 0.009
Tags: @product
2:18.009
Before features/support/hooks.rb:269 0.007
Given a computer 0.264
And I start Tails from USB drive "old" with network unplugged and I login 1:25.613
Then Tails is running from USB drive "old" 0.346
And I create a persistent partition 38.144
And I take note of which tps features are available 3.642
Then a Tails persistence partition exists on USB drive "old" 1.026
And I shutdown Tails and wait for the computer to power off 8.971
After features/support/hooks.rb:326 0.171
After features/support/hooks.rb:100 0.009
Tags: @product
3:5.274
Before features/support/hooks.rb:269 0.007
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:27.754
Then Tails is running from USB drive "old" 0.372
And all tps features are active 2.517
When I write some files expected to persist 1.872
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.235
And all persistence configuration files have safe access rights 0.423
And all persistent directories from the old Tails version have safe access rights 2.493
And I take note of which tps features are available 0.476
And I shutdown Tails and wait for the computer to power off 4.242
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.695
After features/support/hooks.rb:326 0.127
After features/support/hooks.rb:100 0.011
Tags: @product
2:35.664
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.804
And I log in to a new session 22.720
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.758
And I plug USB drive "to_upgrade" 2.401
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.611
Then the running Tails is installed on USB drive "to_upgrade" 21.971
And I unplug USB drive "to_upgrade" 0.201
And I unplug USB drive "__internal" 0.195
After features/support/hooks.rb:326 2.190
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.706
Before features/support/hooks.rb:269 0.007
Given a computer 0.233
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.604
Then all tps features from the old Tails version are active 2.425
And Tails is running from USB drive "to_upgrade" 0.388
And the boot device has safe access rights 3.842
And the expected persistent files created with the old Tails version are present in the filesystem 1.536
And all persistent directories from the old Tails version have safe access rights 2.675
After features/support/hooks.rb:326 0.776
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:8.292
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 34.029
And no SquashFS delta is installed 0.189
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.312
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.725
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.460
When the network is plugged 0.091
And Tor is ready 22.934
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.470
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.061
Given I shutdown Tails and wait for the computer to power off 10.901
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.785
Then Tails is running version 6.2~testoverlayfs 0.041
And all tps features are active 2.425
And the file system changes introduced in version 6.2~testoverlayfs are present 0.339
And only the 6.2~testoverlayfs SquashFS delta is installed 0.135
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.356
# 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.377
When the network is plugged 0.077
And Tor is ready 19.311
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.312
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.931
Given I shutdown Tails and wait for the computer to power off 4.588
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.394
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.312
And the file system changes introduced in version 6.3~testoverlayfs are present 0.802
And only the 6.3~testoverlayfs SquashFS delta is installed 0.096
# 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.437
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.299
When the network is plugged 0.089
And Tor is ready 20.400
Then the Upgrader considers the system as up-to-date 0.369
# 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.044
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.117
After features/support/hooks.rb:326 0.802
After features/support/hooks.rb:100 0.084
Tags: @product @automatic_upgrade
42.079
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.131
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.798
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.142
And the signing key used by the Upgrader is outdated 0.772
But a current signing key is available on our website 0.000
When the network is plugged 0.158
And Tor is ready 22.345
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.728
After features/support/hooks.rb:326 1.625
After features/support/hooks.rb:100 0.000