Project Number Date
test_Tails_ISO_stable 4961 22 Jul 2024, 22:38

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:27.715 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:8.962
Before features/support/hooks.rb:269 0.006
Given a computer 0.185
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 26.880
When I start Tails from USB drive "old" with network unplugged 1:35.835
Then the boot device has safe access rights 4.009
And Tails is running from USB drive "old" 0.318
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.287
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:326 7.046
After features/support/hooks.rb:100 0.008
Tags: @product
2:4.904
Before features/support/hooks.rb:269 0.005
Given a computer 0.193
And I start Tails from USB drive "old" with network unplugged and I login 1:22.609
Then Tails is running from USB drive "old" 0.323
And I create a persistent partition 31.330
And I take note of which tps features are available 1.574
Then a Tails persistence partition exists on USB drive "old" 0.743
And I shutdown Tails and wait for the computer to power off 8.129
After features/support/hooks.rb:326 0.129
After features/support/hooks.rb:100 0.009
Tags: @product
2:35.791
Before features/support/hooks.rb:269 0.006
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:0.588
Then Tails is running from USB drive "old" 0.307
And all tps features are active 1.867
When I write some files expected to persist 1.599
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.195
And all persistence configuration files have safe access rights 0.354
And all persistent directories from the old Tails version have safe access rights 2.301
And I take note of which tps features are available 0.445
And I shutdown Tails and wait for the computer to power off 4.198
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.738
After features/support/hooks.rb:326 0.143
After features/support/hooks.rb:100 0.010
Tags: @product
2:26.599
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 10.028
And I log in to a new session 17.668
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.240
And I plug USB drive "to_upgrade" 2.419
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.418
Then the running Tails is installed on USB drive "to_upgrade" 20.419
And I unplug USB drive "to_upgrade" 0.212
And I unplug USB drive "__internal" 0.191
After features/support/hooks.rb:326 1.975
After features/support/hooks.rb:100 0.000
Tags: @product
2:5.910
Before features/support/hooks.rb:269 0.007
Given a computer 0.190
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:56.943
Then all tps features from the old Tails version are active 1.656
And Tails is running from USB drive "to_upgrade" 0.293
And the boot device has safe access rights 2.936
And the expected persistent files created with the old Tails version are present in the filesystem 1.587
And all persistent directories from the old Tails version have safe access rights 2.302
After features/support/hooks.rb:326 0.736
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:30.691
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 25.421
And no SquashFS delta is installed 0.207
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.514
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.310
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.452
When the network is plugged 0.055
And Tor is ready 23.493
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.947
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.272
Given I shutdown Tails and wait for the computer to power off 8.573
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.385
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.107
And the file system changes introduced in version 6.2~testoverlayfs are present 0.320
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.337
# 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.258
When the network is plugged 0.062
And Tor is ready 17.782
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.397
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.133
Given I shutdown Tails and wait for the computer to power off 4.371
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.245
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.995
And the file system changes introduced in version 6.3~testoverlayfs are present 0.463
And only the 6.3~testoverlayfs SquashFS delta is installed 0.060
# 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.334
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.268
When the network is plugged 0.041
And Tor is ready 16.750
Then the Upgrader considers the system as up-to-date 10.778
# 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 13.321
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.868
After features/support/hooks.rb:326 0.784
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
34.854
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 9.519
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.346
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 1.606
But a current signing key is available on our website 0.000
When the network is plugged 0.075
And Tor is ready 18.352
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.895
After features/support/hooks.rb:326 0.696
After features/support/hooks.rb:100 0.000