Project Number Date
test_Tails_ISO_20522-ocr-more 7 17 Dec 2024, 05:15

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:49.618 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:8.199
Before features/support/hooks.rb:269 0.004
Given a computer 0.196
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 28.567
When I start Tails from USB drive "old" with network unplugged 1:34.411
Then the boot device has safe access rights 2.920
And Tails is running from USB drive "old" 0.315
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.324
And I unplug USB drive "old" 0.198
After features/support/hooks.rb:326 6.730
After features/support/hooks.rb:100 0.009
Tags: @product
2:7.330
Before features/support/hooks.rb:269 0.006
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login 1:22.097
Then Tails is running from USB drive "old" 0.330
And I create a persistent partition 34.366
And I take note of which tps features are available 1.367
Then a Tails persistence partition exists on USB drive "old" 0.785
And I shutdown Tails and wait for the computer to power off 8.191
After features/support/hooks.rb:326 0.264
After features/support/hooks.rb:100 0.009
Tags: @product
2:49.538
Before features/support/hooks.rb:269 0.006
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.483
Then Tails is running from USB drive "old" 0.876
And all tps features are active 1.966
When I write some files expected to persist 2.051
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.221
And all persistence configuration files have safe access rights 0.420
And all persistent directories from the old Tails version have safe access rights 2.537
And I take note of which tps features are available 0.461
And I shutdown Tails and wait for the computer to power off 4.317
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.017
After features/support/hooks.rb:326 0.125
After features/support/hooks.rb:100 0.008
Tags: @product
2:32.133
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.784
And I log in to a new session 20.977
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.566
And I plug USB drive "to_upgrade" 3.125
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.641
Then the running Tails is installed on USB drive "to_upgrade" 21.610
And I unplug USB drive "to_upgrade" 0.224
And I unplug USB drive "__internal" 0.203
After features/support/hooks.rb:326 2.318
After features/support/hooks.rb:100 0.000
Tags: @product
2:5.052
Before features/support/hooks.rb:269 0.006
Given a computer 0.206
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:55.638
Then all tps features from the old Tails version are active 1.647
And Tails is running from USB drive "to_upgrade" 0.331
And the boot device has safe access rights 3.409
And the expected persistent files created with the old Tails version are present in the filesystem 1.363
And all persistent directories from the old Tails version have safe access rights 2.455
After features/support/hooks.rb:326 0.963
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:29.254
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 11.408
And no SquashFS delta is installed 0.185
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.331
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.265
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.416
When the network is plugged 0.098
And Tor is ready 22.657
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.513
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.618
Given I shutdown Tails and wait for the computer to power off 8.684
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.131
Then Tails is running version 6.2~testoverlayfs 0.025
And all tps features are active 2.190
And the file system changes introduced in version 6.2~testoverlayfs are present 0.333
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.283
# 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.317
When the network is plugged 0.096
And Tor is ready 18.761
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.088
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.371
Given I shutdown Tails and wait for the computer to power off 4.303
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.625
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.155
And the file system changes introduced in version 6.3~testoverlayfs are present 0.448
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.317
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.243
When the network is plugged 0.078
And Tor is ready 17.915
Then the Upgrader considers the system as up-to-date 10.797
# 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 16.210
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.164
After features/support/hooks.rb:326 0.708
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
38.110
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.024
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.392
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.091
And the signing key used by the Upgrader is outdated 0.763
But a current signing key is available on our website 0.000
When the network is plugged 0.092
And Tor is ready 21.427
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.318
After features/support/hooks.rb:326 0.657
After features/support/hooks.rb:100 0.000