Project Number Date
test_Tails_ISO_stable 4710 11 Mar 2024, 19:37

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:41.431 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:51.282
Before features/support/hooks.rb:245 0.005
Given a computer 0.181
And I create a 7200 MiB disk named "old" 0.056
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 21.203
When I start Tails from USB drive "old" with network unplugged 1:24.383
Then the boot device has safe access rights 3.272
And Tails is running from USB drive "old" 0.349
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.426
And I unplug USB drive "old" 0.197
After features/support/hooks.rb:291 3.584
After features/support/hooks.rb:75 0.010
Tags: @product
2:10.376
Before features/support/hooks.rb:245 0.006
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login 1:17.575
Then Tails is running from USB drive "old" 0.309
And I create a persistent partition 41.547
And I take note of which tps features are available 1.932
Then a Tails persistence partition exists on USB drive "old" 0.782
And I shutdown Tails and wait for the computer to power off 8.049
After features/support/hooks.rb:291 0.132
After features/support/hooks.rb:75 0.008
Tags: @product
2:36.428
Before features/support/hooks.rb:245 0.004
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:9.541
Then Tails is running from USB drive "old" 0.373
And all tps features are active 1.796
When I write some files expected to persist 1.533
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.232
And all persistence configuration files have safe access rights 0.341
And all persistent directories from the old Tails version have safe access rights 2.793
And I take note of which tps features are available 0.533
And I shutdown Tails and wait for the computer to power off 4.018
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.075
After features/support/hooks.rb:291 0.115
After features/support/hooks.rb:75 0.009
Tags: @product
2:30.488
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 10.560
And I log in to a new session 18.662
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.345
And I plug USB drive "to_upgrade" 2.452
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.806
Then the running Tails is installed on USB drive "to_upgrade" 14.269
And I unplug USB drive "to_upgrade" 0.199
And I unplug USB drive "__internal" 0.191
After features/support/hooks.rb:291 3.496
After features/support/hooks.rb:75 0.000
Tags: @product
2:22.268
Before features/support/hooks.rb:245 0.006
Given a computer 0.187
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.525
Then all tps features from the old Tails version are active 1.306
And Tails is running from USB drive "to_upgrade" 0.377
And the boot device has safe access rights 3.030
And the expected persistent files created with the old Tails version are present in the filesystem 1.494
And all persistent directories from the old Tails version have safe access rights 2.346
After features/support/hooks.rb:291 0.750
After features/support/hooks.rb:75 0.009
Tags: @product @automatic_upgrade
6:36.738
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.195
And no SquashFS delta is installed 0.088
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.293
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.266
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.467
When the network is plugged 0.097
And Tor is ready 17.616
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.805
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.954
Given I shutdown Tails and wait for the computer to power off 6.070
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.471
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.123
And the file system changes introduced in version 6.2~testoverlayfs are present 0.318
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.305
# 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.285
When the network is plugged 0.037
And Tor is ready 15.386
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.526
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.365
Given I shutdown Tails and wait for the computer to power off 4.110
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.237
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.838
And the file system changes introduced in version 6.3~testoverlayfs are present 0.492
And only the 6.3~testoverlayfs SquashFS delta is installed 0.097
# 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.366
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.230
When the network is plugged 0.035
And Tor is ready 16.743
Then the Upgrader considers the system as up-to-date 0.253
# 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.441
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.055
After features/support/hooks.rb:291 0.749
After features/support/hooks.rb:75 0.020
Tags: @product @automatic_upgrade
33.848
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 9.913
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.307
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.487
But a current signing key is available on our website 0.000
When the network is plugged 0.043
And Tor is ready 19.333
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.706
After features/support/hooks.rb:291 0.801
After features/support/hooks.rb:75 0.000