Project Number Date
test_Tails_ISO_stable 5158 08 Oct 2024, 12:29

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:39.361 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:6.029
Before features/support/hooks.rb:269 0.005
Given a computer 0.185
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 30.252
When I start Tails from USB drive "old" with network unplugged 1:30.342
Then the boot device has safe access rights 3.103
And Tails is running from USB drive "old" 0.353
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.104
And udev-watchdog is monitoring the correct device 0.325
And I unplug USB drive "old" 0.192
After features/support/hooks.rb:326 3.560
After features/support/hooks.rb:100 0.009
Tags: @product
2:10.588
Before features/support/hooks.rb:269 0.006
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login 1:28.032
Then Tails is running from USB drive "old" 0.307
And I create a persistent partition 31.546
And I take note of which tps features are available 1.384
Then a Tails persistence partition exists on USB drive "old" 0.831
And I shutdown Tails and wait for the computer to power off 8.287
After features/support/hooks.rb:326 0.130
After features/support/hooks.rb:100 0.009
Tags: @product
2:51.322
Before features/support/hooks.rb:269 0.005
Given a computer 0.170
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.760
Then Tails is running from USB drive "old" 0.327
And all tps features are active 1.817
When I write some files expected to persist 1.717
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.206
And all persistence configuration files have safe access rights 0.392
And all persistent directories from the old Tails version have safe access rights 2.288
And I take note of which tps features are available 0.379
And I shutdown Tails and wait for the computer to power off 4.228
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.033
After features/support/hooks.rb:326 0.136
After features/support/hooks.rb:100 0.009
Tags: @product
2:28.136
Before features/support/hooks.rb:269 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 11.025
And I log in to a new session 18.124
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.037
And I plug USB drive "to_upgrade" 2.390
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.114
Then the running Tails is installed on USB drive "to_upgrade" 21.030
And I unplug USB drive "to_upgrade" 0.195
And I unplug USB drive "__internal" 0.219
After features/support/hooks.rb:326 1.938
After features/support/hooks.rb:100 0.000
Tags: @product
2:8.184
Before features/support/hooks.rb:269 0.006
Given a computer 0.175
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:59.005
Then all tps features from the old Tails version are active 1.506
And Tails is running from USB drive "to_upgrade" 0.332
And the boot device has safe access rights 3.369
And the expected persistent files created with the old Tails version are present in the filesystem 1.477
And all persistent directories from the old Tails version have safe access rights 2.316
After features/support/hooks.rb:326 0.572
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:21.043
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 11.659
And no SquashFS delta is installed 0.096
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.295
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.294
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.433
When the network is plugged 0.076
And Tor is ready 18.372
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.357
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.407
Given I shutdown Tails and wait for the computer to power off 8.537
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.775
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.086
And the file system changes introduced in version 6.2~testoverlayfs are present 0.274
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.340
# 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.294
When the network is plugged 0.060
And Tor is ready 48.262
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.571
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.714
Given I shutdown Tails and wait for the computer to power off 4.614
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:50.320
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.877
And the file system changes introduced in version 6.3~testoverlayfs are present 0.463
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.289
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.248
When the network is plugged 0.101
And Tor is ready 19.027
Then the Upgrader considers the system as up-to-date 0.308
# 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.743
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.925
After features/support/hooks.rb:326 0.656
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
34.057
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 9.708
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.368
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 0.732
But a current signing key is available on our website 0.000
When the network is plugged 0.066
And Tor is ready 18.085
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.030
After features/support/hooks.rb:326 0.659
After features/support/hooks.rb:100 0.000