Project Number Date
test_Tails_ISO_stable 4688 29 Feb 2024, 17:26

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 17:35.824 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
1:29.076
Before features/support/hooks.rb:245 0.006
Given a computer 0.158
And I create a 7200 MiB disk named "old" 0.032
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 18.768
When I start Tails from USB drive "old" with network unplugged 1:5.269
Then the boot device has safe access rights 2.841
And Tails is running from USB drive "old" 0.319
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.309
And I unplug USB drive "old" 0.174
After features/support/hooks.rb:291 6.769
After features/support/hooks.rb:75 0.009
Tags: @product
2:2.306
Before features/support/hooks.rb:245 0.007
Given a computer 0.152
And I start Tails from USB drive "old" with network unplugged and I login 1:10.391
Then Tails is running from USB drive "old" 0.330
And I create a persistent partition 40.855
And I take note of which tps features are available 1.797
Then a Tails persistence partition exists on USB drive "old" 0.749
And I shutdown Tails and wait for the computer to power off 8.028
After features/support/hooks.rb:291 0.161
After features/support/hooks.rb:75 0.008
Tags: @product
2:31.073
Before features/support/hooks.rb:245 0.004
Given a computer 0.156
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:5.196
Then Tails is running from USB drive "old" 0.339
And all tps features are active 1.900
When I write some files expected to persist 1.583
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.189
And all persistence configuration files have safe access rights 0.381
And all persistent directories from the old Tails version have safe access rights 2.319
And I take note of which tps features are available 0.372
And I shutdown Tails and wait for the computer to power off 4.147
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.488
After features/support/hooks.rb:291 0.158
After features/support/hooks.rb:75 0.009
Tags: @product
2:26.270
Before features/support/hooks.rb:245 0.009
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.980
And I log in to a new session 14.793
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.264
And I plug USB drive "to_upgrade" 2.408
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:45.207
Then the running Tails is installed on USB drive "to_upgrade" 12.231
And I unplug USB drive "to_upgrade" 0.205
And I unplug USB drive "__internal" 0.179
After features/support/hooks.rb:291 20:0.802
After features/support/hooks.rb:75 0.000
Tags: @product
2:17.709
Before features/support/hooks.rb:245 0.006
Given a computer 0.179
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.921
Then all tps features from the old Tails version are active 1.369
And Tails is running from USB drive "to_upgrade" 0.332
And the boot device has safe access rights 3.173
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.302
After features/support/hooks.rb:291 0.603
After features/support/hooks.rb:75 0.011
Tags: @product @automatic_upgrade
6:18.513
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.971
And no SquashFS delta is installed 0.217
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.306
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.306
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.506
When the network is plugged 0.043
And Tor is ready 16.410
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.344
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.337
Given I shutdown Tails and wait for the computer to power off 6.021
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.565
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 1.812
And the file system changes introduced in version 6.2~testoverlayfs are present 0.263
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.299
# 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.231
When the network is plugged 0.036
And Tor is ready 16.724
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.610
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.157
Given I shutdown Tails and wait for the computer to power off 4.024
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.821
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.660
And the file system changes introduced in version 6.3~testoverlayfs are present 0.490
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.310
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.277
When the network is plugged 0.024
And Tor is ready 17.118
Then the Upgrader considers the system as up-to-date 0.256
# 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.284
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.842
After features/support/hooks.rb:291 0.691
After features/support/hooks.rb:75 0.020
Tags: @product @automatic_upgrade
30.874
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.117
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.321
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.082
And the signing key used by the Upgrader is outdated 0.579
But a current signing key is available on our website 0.000
When the network is plugged 0.025
And Tor is ready 14.517
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.231
After features/support/hooks.rb:291 1.247
After features/support/hooks.rb:75 0.000