Project Number Date
test_Tails_ISO_20263-test-suite-without-spice 14 21 Mar 2025, 02:27

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:17.226 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
1:57.676
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.206
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 28.829
When I start Tails from USB drive "old" with network unplugged 1:23.343
Then the boot device has safe access rights 3.271
And Tails is running from USB drive "old" 0.295
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.088
And udev-watchdog is monitoring the correct device 0.293
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:330 9.382
After features/support/hooks.rb:100 0.008
Tags: @product
2:2.799
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login 1:22.930
Then Tails is running from USB drive "old" 0.319
And I create a persistent partition 30.790
And I take note of which tps features are available 1.495
Then a Tails persistence partition exists on USB drive "old" 0.817
And I shutdown Tails and wait for the computer to power off 6.263
After features/support/hooks.rb:330 0.143
After features/support/hooks.rb:100 0.008
Tags: @product
2:46.312
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.348
Then Tails is running from USB drive "old" 0.280
And all tps features are active 1.693
When I write some files expected to persist 1.437
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.189
And all persistence configuration files have safe access rights 0.348
And all persistent directories from the old Tails version have safe access rights 2.101
And I take note of which tps features are available 0.391
And I shutdown Tails and wait for the computer to power off 4.206
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.119
After features/support/hooks.rb:330 0.160
After features/support/hooks.rb:100 0.009
Tags: @product
2:25.217
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.721
And I log in to a new session 20.580
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.369
And I plug USB drive "to_upgrade" 2.428
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.127
Then the running Tails is installed on USB drive "to_upgrade" 16.560
And I unplug USB drive "to_upgrade" 0.212
And I unplug USB drive "__internal" 0.216
After features/support/hooks.rb:330 3.054
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.589
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 "to_upgrade" with network unplugged and I login with persistence enabled 2:3.704
Then all tps features from the old Tails version are active 1.789
And Tails is running from USB drive "to_upgrade" 0.326
And the boot device has safe access rights 2.909
And the expected persistent files created with the old Tails version are present in the filesystem 1.421
And all persistent directories from the old Tails version have safe access rights 2.264
After features/support/hooks.rb:330 1.373
After features/support/hooks.rb:100 0.008
6:20.218
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.541
And no SquashFS delta is installed 0.179
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.343
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.277
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.512
When the network is plugged 0.063
And Tor is ready 21.440
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.367
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.106
Given I shutdown Tails and wait for the computer to power off 8.561
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.970
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.127
And the file system changes introduced in version 6.2~testoverlayfs are present 0.273
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.276
# 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.068
And Tor is ready 17.807
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.016
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.260
Given I shutdown Tails and wait for the computer to power off 4.391
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.820
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.854
And the file system changes introduced in version 6.3~testoverlayfs are present 0.441
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.247
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.255
When the network is plugged 0.083
And Tor is ready 19.354
Then the Upgrader considers the system as up-to-date 0.298
# 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.815
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.979
After features/support/hooks.rb:330 0.710
After features/support/hooks.rb:100 0.017
32.411
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.335
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.417
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.117
And the signing key used by the Upgrader is outdated 0.083
But a current signing key is available on our website 0.000
When the network is plugged 0.093
And Tor is ready 15.932
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.431
After features/support/hooks.rb:330 0.908
After features/support/hooks.rb:100 0.000