Project Number Date
test_Tails_ISO_20263-test-suite-without-spice 19 26 Mar 2025, 02:43

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:18.100 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:9.317
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.213
And I create a 7200 MiB disk named "old" 0.057
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 28.831
When I start Tails from USB drive "old" with network unplugged 1:34.707
Then the boot device has safe access rights 3.401
And Tails is running from USB drive "old" 0.371
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.106
And udev-watchdog is monitoring the correct device 0.287
And I unplug USB drive "old" 0.210
After features/support/hooks.rb:330 9.601
After features/support/hooks.rb:100 0.008
Tags: @product
2:5.330
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login 1:22.444
Then Tails is running from USB drive "old" 0.342
And I create a persistent partition 31.687
And I take note of which tps features are available 1.316
Then a Tails persistence partition exists on USB drive "old" 0.810
And I shutdown Tails and wait for the computer to power off 8.546
After features/support/hooks.rb:330 0.172
After features/support/hooks.rb:100 0.008
Tags: @product
2:53.156
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.174
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.310
Then Tails is running from USB drive "old" 0.696
And all tps features are active 2.090
When I write some files expected to persist 2.622
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.200
And all persistence configuration files have safe access rights 0.376
And all persistent directories from the old Tails version have safe access rights 2.367
And I take note of which tps features are available 0.436
And I shutdown Tails and wait for the computer to power off 4.216
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.664
After features/support/hooks.rb:330 0.103
After features/support/hooks.rb:100 0.008
Tags: @product
2:33.131
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 without a persistent partition and stopped at Tails Greeter's login screen 10.548
And I log in to a new session 21.234
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.559
And I plug USB drive "to_upgrade" 2.408
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.137
Then the running Tails is installed on USB drive "to_upgrade" 21.809
And I unplug USB drive "to_upgrade" 0.219
And I unplug USB drive "__internal" 0.214
After features/support/hooks.rb:330 3.599
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.457
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.198
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:15.266
Then all tps features from the old Tails version are active 1.738
And Tails is running from USB drive "to_upgrade" 0.316
And the boot device has safe access rights 3.255
And the expected persistent files created with the old Tails version are present in the filesystem 1.289
And all persistent directories from the old Tails version have safe access rights 2.391
After features/support/hooks.rb:330 1.434
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:37.279
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 11.345
And no SquashFS delta is installed 0.222
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.300
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.390
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.493
When the network is plugged 0.118
And Tor is ready 21.259
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.684
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.903
Given I shutdown Tails and wait for the computer to power off 1:22.395
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.072
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.380
And the file system changes introduced in version 6.2~testoverlayfs are present 0.315
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.286
# 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.252
When the network is plugged 0.080
And Tor is ready 18.789
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.374
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.094
Given I shutdown Tails and wait for the computer to power off 4.552
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.372
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.039
And the file system changes introduced in version 6.3~testoverlayfs are present 0.461
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.338
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.220
When the network is plugged 0.068
And Tor is ready 19.323
Then the Upgrader considers the system as up-to-date 0.317
# 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.484
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.112
After features/support/hooks.rb:330 0.746
After features/support/hooks.rb:100 0.091
Tags: @product @automatic_upgrade
35.427
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 9.913
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.469
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.087
But a current signing key is available on our website 0.000
When the network is plugged 0.076
And Tor is ready 18.451
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.377
After features/support/hooks.rb:330 0.672
After features/support/hooks.rb:100 0.000