Project Number Date
test_Tails_ISO_devel 3656 21 Jan 2025, 17:35

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:56.593 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:2.350
Before features/support/hooks.rb:269 0.003
Given a computer 0.492
And I create a 7200 MiB disk named "old" 0.190
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 30.068
When I start Tails from USB drive "old" with network unplugged 1:26.671
Then the boot device has safe access rights 2.875
And Tails is running from USB drive "old" 0.294
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.339
And I unplug USB drive "old" 0.207
After features/support/hooks.rb:326 6.980
After features/support/hooks.rb:100 0.005
Tags: @product
2:2.793
Before features/support/hooks.rb:269 0.002
Given a computer 0.169
And I start Tails from USB drive "old" with network unplugged and I login 1:19.552
Then Tails is running from USB drive "old" 0.310
And I create a persistent partition 32.109
And I take note of which tps features are available 1.534
Then a Tails persistence partition exists on USB drive "old" 0.853
And I shutdown Tails and wait for the computer to power off 8.262
After features/support/hooks.rb:326 0.140
After features/support/hooks.rb:100 0.007
Tags: @product
2:45.833
Before features/support/hooks.rb:269 0.003
Given a computer 0.175
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:9.727
Then Tails is running from USB drive "old" 0.602
And all tps features are active 1.840
When I write some files expected to persist 1.703
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.207
And all persistence configuration files have safe access rights 0.353
And all persistent directories from the old Tails version have safe access rights 2.437
And I take note of which tps features are available 0.409
And I shutdown Tails and wait for the computer to power off 4.473
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.902
After features/support/hooks.rb:326 0.096
After features/support/hooks.rb:100 0.006
Tags: @product
2:28.333
Before features/support/hooks.rb:269 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.608
And I log in to a new session 19.127
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.488
And I plug USB drive "to_upgrade" 2.503
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.567
Then the running Tails is installed on USB drive "to_upgrade" 21.632
And I unplug USB drive "to_upgrade" 0.205
And I unplug USB drive "__internal" 0.201
After features/support/hooks.rb:326 2.656
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.166
Before features/support/hooks.rb:269 0.003
Given a computer 0.161
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.721
Then all tps features from the old Tails version are active 1.746
And Tails is running from USB drive "to_upgrade" 0.349
And the boot device has safe access rights 3.571
And the expected persistent files created with the old Tails version are present in the filesystem 1.354
And all persistent directories from the old Tails version have safe access rights 2.260
After features/support/hooks.rb:326 0.829
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
6:50.572
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.585
And no SquashFS delta is installed 0.217
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.298
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.263
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.429
When the network is plugged 0.060
And Tor is ready 19.140
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.299
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.532
Given I shutdown Tails and wait for the computer to power off 9.082
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.452
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.077
And the file system changes introduced in version 6.2~testoverlayfs are present 0.353
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.458
# 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.343
When the network is plugged 0.069
And Tor is ready 19.507
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.450
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.009
Given I shutdown Tails and wait for the computer to power off 4.216
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.233
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.989
And the file system changes introduced in version 6.3~testoverlayfs are present 0.433
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.371
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.241
When the network is plugged 0.089
And Tor is ready 47.698
Then the Upgrader considers the system as up-to-date 0.278
# 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 14.133
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.047
After features/support/hooks.rb:326 0.703
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
34.544
Before features/support/hooks.rb:269 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.026
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.047
And the signing key used by the Upgrader is outdated 0.059
But a current signing key is available on our website 0.000
When the network is plugged 0.144
And Tor is ready 17.485
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.468
After features/support/hooks.rb:326 0.675
After features/support/hooks.rb:100 0.000