Project Number Date
test_Tails_ISO_20263-test-suite-without-spice 2 08 Mar 2025, 03:04

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 19:52.174 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:3.794
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.183
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 29.013
When I start Tails from USB drive "old" with network unplugged 1:28.902
Then the boot device has safe access rights 3.461
And Tails is running from USB drive "old" 0.325
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.304
And I unplug USB drive "old" 0.332
After features/support/hooks.rb:330 3.575
After features/support/hooks.rb:100 0.009
Tags: @product
2:12.614
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.214
And I start Tails from USB drive "old" with network unplugged and I login 1:27.829
Then Tails is running from USB drive "old" 0.391
And I create a persistent partition 31.238
And I take note of which tps features are available 1.580
Then a Tails persistence partition exists on USB drive "old" 0.808
And I shutdown Tails and wait for the computer to power off 10.551
After features/support/hooks.rb:330 0.169
After features/support/hooks.rb:100 0.009
Tags: @product
2:51.009
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.242
Then Tails is running from USB drive "old" 0.381
And all tps features are active 2.132
When I write some files expected to persist 1.801
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.298
And all persistence configuration files have safe access rights 0.371
And all persistent directories from the old Tails version have safe access rights 2.771
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.226
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.118
After features/support/hooks.rb:330 0.119
After features/support/hooks.rb:100 0.010
Tags: @product
2:29.251
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 10.431
And I log in to a new session 20.009
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.460
And I plug USB drive "to_upgrade" 2.401
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.172
Then the running Tails is installed on USB drive "to_upgrade" 21.272
And I unplug USB drive "to_upgrade" 0.254
And I unplug USB drive "__internal" 0.248
After features/support/hooks.rb:330 2.419
After features/support/hooks.rb:100 0.000
Tags: @product
2:29.791
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.256
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:20.120
Then all tps features from the old Tails version are active 1.823
And Tails is running from USB drive "to_upgrade" 0.427
And the boot device has safe access rights 3.219
And the expected persistent files created with the old Tails version are present in the filesystem 1.412
And all persistent directories from the old Tails version have safe access rights 2.531
After features/support/hooks.rb:330 1.277
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:48.095
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.780
And no SquashFS delta is installed 0.230
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.499
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.285
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.497
When the network is plugged 0.070
And Tor is ready 19.154
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.654
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.485
Given I shutdown Tails and wait for the computer to power off 9.114
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:19.386
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.468
And the file system changes introduced in version 6.2~testoverlayfs are present 0.348
And only the 6.2~testoverlayfs SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.303
# 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.263
When the network is plugged 0.086
And Tor is ready 16.706
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.844
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.622
Given I shutdown Tails and wait for the computer to power off 4.442
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.324
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.113
And the file system changes introduced in version 6.3~testoverlayfs are present 0.494
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.278
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.301
When the network is plugged 0.068
And Tor is ready 17.708
Then the Upgrader considers the system as up-to-date 0.323
# 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.879
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.120
After features/support/hooks.rb:330 0.748
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
57.618
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.205
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.981
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.157
And the signing key used by the Upgrader is outdated 0.126
But a current signing key is available on our website 0.000
When the network is plugged 0.072
And Tor is ready 46.511
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.563
After features/support/hooks.rb:330 0.676
After features/support/hooks.rb:100 0.000