Project Number Date
test_Tails_ISO_stable 5162 09 Oct 2024, 12:52

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:17.478 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.124
Before features/support/hooks.rb:269 0.005
Given a computer 0.371
And I create a 7200 MiB disk named "old" 0.121
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 32.299
When I start Tails from USB drive "old" with network unplugged 1:29.928
Then the boot device has safe access rights 3.298
And Tails is running from USB drive "old" 0.322
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.360
And I unplug USB drive "old" 0.199
After features/support/hooks.rb:326 7.276
After features/support/hooks.rb:100 0.007
Tags: @product
2:27.169
Before features/support/hooks.rb:269 0.005
Given a computer 0.204
And I start Tails from USB drive "old" with network unplugged and I login 1:27.001
Then Tails is running from USB drive "old" 0.375
And I create a persistent partition 39.133
And I take note of which tps features are available 8.947
Then a Tails persistence partition exists on USB drive "old" 0.807
And I shutdown Tails and wait for the computer to power off 10.700
After features/support/hooks.rb:326 0.169
After features/support/hooks.rb:100 0.010
Tags: @product
3:20.012
Before features/support/hooks.rb:269 0.004
Given a computer 1.545
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:38.469
Then Tails is running from USB drive "old" 1.818
And all tps features are active 2.293
When I write some files expected to persist 2.868
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.232
And all persistence configuration files have safe access rights 0.450
And all persistent directories from the old Tails version have safe access rights 2.512
And I take note of which tps features are available 0.617
And I shutdown Tails and wait for the computer to power off 4.451
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.752
After features/support/hooks.rb:326 0.150
After features/support/hooks.rb:100 0.009
Tags: @product
3:1.969
Before features/support/hooks.rb:269 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 28.018
And I log in to a new session 20.749
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.525
And I plug USB drive "to_upgrade" 2.512
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.571
Then the running Tails is installed on USB drive "to_upgrade" 27.101
And I unplug USB drive "to_upgrade" 0.213
And I unplug USB drive "__internal" 0.277
After features/support/hooks.rb:326 1.813
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.782
Before features/support/hooks.rb:269 0.005
Given a computer 0.265
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.652
Then all tps features from the old Tails version are active 1.986
And Tails is running from USB drive "to_upgrade" 0.357
And the boot device has safe access rights 3.347
And the expected persistent files created with the old Tails version are present in the filesystem 1.615
And all persistent directories from the old Tails version have safe access rights 2.557
After features/support/hooks.rb:326 1.016
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:22.481
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 11.921
And no SquashFS delta is installed 0.107
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.311
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.079
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.313
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.481
When the network is plugged 0.089
And Tor is ready 19.038
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.633
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.138
Given I shutdown Tails and wait for the computer to power off 8.503
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.687
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.338
And the file system changes introduced in version 6.2~testoverlayfs are present 0.286
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.447
# 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.250
When the network is plugged 0.068
And Tor is ready 16.873
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.742
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.229
Given I shutdown Tails and wait for the computer to power off 4.520
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.285
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.329
And the file system changes introduced in version 6.3~testoverlayfs are present 0.553
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.333
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.350
When the network is plugged 0.098
And Tor is ready 17.584
Then the Upgrader considers the system as up-to-date 10.866
# 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 13.974
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.864
After features/support/hooks.rb:326 0.881
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
37.938
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.424
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.341
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the signing key used by the Upgrader is outdated 0.820
But a current signing key is available on our website 0.000
When the network is plugged 0.066
And Tor is ready 19.339
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.873
After features/support/hooks.rb:326 0.749
After features/support/hooks.rb:100 0.000