Project Number Date
test_Tails_ISO_devel 3453 09 Jul 2024, 14:50

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:51.290 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.892
Before features/support/hooks.rb:269 0.006
Given a computer 0.220
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.062
And I write an old version of the Tails USB image to disk "old" 34.539
When I start Tails from USB drive "old" with network unplugged 1:40.128
Then the boot device has safe access rights 2.924
And Tails is running from USB drive "old" 0.339
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.086
And udev-watchdog is monitoring the correct device 0.289
And I unplug USB drive "old" 0.194
After features/support/hooks.rb:326 8.043
After features/support/hooks.rb:100 0.013
Tags: @product
2:4.234
Before features/support/hooks.rb:269 0.009
Given a computer 0.225
And I start Tails from USB drive "old" with network unplugged and I login 1:19.431
Then Tails is running from USB drive "old" 0.327
And I create a persistent partition 33.616
And I take note of which tps features are available 1.400
Then a Tails persistence partition exists on USB drive "old" 0.883
And I shutdown Tails and wait for the computer to power off 8.349
After features/support/hooks.rb:326 0.168
After features/support/hooks.rb:100 0.011
Tags: @product
2:56.947
Before features/support/hooks.rb:269 0.008
Given a computer 0.281
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.593
Then Tails is running from USB drive "old" 0.419
And all tps features are active 2.650
When I write some files expected to persist 1.674
# 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.374
And all persistent directories from the old Tails version have safe access rights 2.463
And I take note of which tps features are available 0.559
And I shutdown Tails and wait for the computer to power off 4.372
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.326
After features/support/hooks.rb:326 0.120
After features/support/hooks.rb:100 0.011
Tags: @product
2:33.041
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.650
And I log in to a new session 17.134
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.676
And I plug USB drive "to_upgrade" 2.398
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.420
Then the running Tails is installed on USB drive "to_upgrade" 21.347
And I unplug USB drive "to_upgrade" 0.210
And I unplug USB drive "__internal" 0.203
After features/support/hooks.rb:326 6.966
After features/support/hooks.rb:100 0.000
Tags: @product
2:8.931
Before features/support/hooks.rb:269 0.008
Given a computer 0.250
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:59.516
Then all tps features from the old Tails version are active 1.630
And Tails is running from USB drive "to_upgrade" 0.335
And the boot device has safe access rights 2.981
And the expected persistent files created with the old Tails version are present in the filesystem 1.721
And all persistent directories from the old Tails version have safe access rights 2.495
After features/support/hooks.rb:326 1.048
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:12.613
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.736
And no SquashFS delta is installed 0.153
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.425
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.103
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.298
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.396
When the network is plugged 0.033
And Tor is ready 20.175
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.752
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.397
Given I shutdown Tails and wait for the computer to power off 8.766
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.480
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.194
And the file system changes introduced in version 6.2~testoverlayfs are present 0.316
And only the 6.2~testoverlayfs SquashFS delta is installed 0.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.425
# 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.254
When the network is plugged 0.047
And Tor is ready 15.862
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.538
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.238
Given I shutdown Tails and wait for the computer to power off 4.451
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.339
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.137
And the file system changes introduced in version 6.3~testoverlayfs are present 0.440
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.335
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.306
When the network is plugged 0.036
And Tor is ready 17.305
Then the Upgrader considers the system as up-to-date 0.319
# 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.195
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.984
After features/support/hooks.rb:326 0.735
After features/support/hooks.rb:100 0.027
Tags: @product @automatic_upgrade
35.630
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.001
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.282
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 1.230
But a current signing key is available on our website 0.000
When the network is plugged 0.067
And Tor is ready 17.437
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.561
After features/support/hooks.rb:326 1.057
After features/support/hooks.rb:100 0.000