Project Number Date
test_Tails_ISO_stable 5312 04 Dec 2024, 12:54

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 20:37.477 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:52.737
Before features/support/hooks.rb:269 0.004
Given a computer 0.275
And I create a 7200 MiB disk named "old" 0.089
And I plug USB drive "old" 1.066
And I write an old version of the Tails USB image to disk "old" 57.047
When I start Tails from USB drive "old" with network unplugged 1:48.533
Then the boot device has safe access rights 4.609
And Tails is running from USB drive "old" 0.329
And there is no persistence partition on USB drive "old" 0.091
And process "udev-watchdog" is running 0.122
And udev-watchdog is monitoring the correct device 0.362
And I unplug USB drive "old" 0.209
After features/support/hooks.rb:326 3.618
After features/support/hooks.rb:100 0.011
Tags: @product
2:26.008
Before features/support/hooks.rb:269 0.005
Given a computer 0.380
And I start Tails from USB drive "old" with network unplugged and I login 1:40.512
Then Tails is running from USB drive "old" 0.401
And I create a persistent partition 32.323
And I take note of which tps features are available 2.234
Then a Tails persistence partition exists on USB drive "old" 0.966
And I shutdown Tails and wait for the computer to power off 9.189
After features/support/hooks.rb:326 0.329
After features/support/hooks.rb:100 0.027
Tags: @product
3:2.791
Before features/support/hooks.rb:269 0.012
Given a computer 0.261
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.068
Then Tails is running from USB drive "old" 1.310
And all tps features are active 1.974
When I write some files expected to persist 3.146
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.229
And all persistence configuration files have safe access rights 0.389
And all persistent directories from the old Tails version have safe access rights 2.506
And I take note of which tps features are available 0.474
And I shutdown Tails and wait for the computer to power off 4.050
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.379
After features/support/hooks.rb:326 0.146
After features/support/hooks.rb:100 0.010
Tags: @product
2:39.302
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.983
And I log in to a new session 22.815
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.890
And I plug USB drive "to_upgrade" 2.830
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.405
Then the running Tails is installed on USB drive "to_upgrade" 23.929
And I unplug USB drive "to_upgrade" 0.226
And I unplug USB drive "__internal" 0.221
After features/support/hooks.rb:326 3.674
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.178
Before features/support/hooks.rb:269 0.004
Given a computer 0.183
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.400
Then all tps features from the old Tails version are active 1.658
And Tails is running from USB drive "to_upgrade" 0.336
And the boot device has safe access rights 3.461
And the expected persistent files created with the old Tails version are present in the filesystem 1.560
And all persistent directories from the old Tails version have safe access rights 2.578
After features/support/hooks.rb:326 1.123
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
6:36.510
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.162
And no SquashFS delta is installed 0.182
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.348
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.112
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.293
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.429
When the network is plugged 0.081
And Tor is ready 23.083
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.823
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.746
Given I shutdown Tails and wait for the computer to power off 10.843
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.779
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.216
And the file system changes introduced in version 6.2~testoverlayfs are present 0.350
And only the 6.2~testoverlayfs SquashFS delta is installed 0.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.298
# 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.092
And Tor is ready 19.176
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.507
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.844
Given I shutdown Tails and wait for the computer to power off 4.509
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.513
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.132
And the file system changes introduced in version 6.3~testoverlayfs are present 0.687
And only the 6.3~testoverlayfs SquashFS delta is installed 0.094
# 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.315
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.279
When the network is plugged 0.081
And Tor is ready 17.412
Then the Upgrader considers the system as up-to-date 0.332
# 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 15.377
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.026
After features/support/hooks.rb:326 0.761
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
40.947
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.817
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.795
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.857
But a current signing key is available on our website 0.000
When the network is plugged 0.075
And Tor is ready 22.106
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.233
After features/support/hooks.rb:326 1.319
After features/support/hooks.rb:100 0.000