Project Number Date
test_Tails_ISO_stable 4912 25 Jun 2024, 12:47

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:9.292 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.336
Before features/support/hooks.rb:269 0.006
Given a computer 0.210
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 30.809
When I start Tails from USB drive "old" with network unplugged 1:32.446
Then the boot device has safe access rights 2.788
And Tails is running from USB drive "old" 0.330
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.313
And I unplug USB drive "old" 0.178
After features/support/hooks.rb:326 3.737
After features/support/hooks.rb:100 0.010
Tags: @product
2:2.449
Before features/support/hooks.rb:269 0.007
Given a computer 0.214
And I start Tails from USB drive "old" with network unplugged and I login 1:21.197
Then Tails is running from USB drive "old" 0.357
And I create a persistent partition 30.565
And I take note of which tps features are available 1.191
Then a Tails persistence partition exists on USB drive "old" 0.744
And I shutdown Tails and wait for the computer to power off 8.177
After features/support/hooks.rb:326 0.158
After features/support/hooks.rb:100 0.011
Tags: @product
2:45.320
Before features/support/hooks.rb:269 0.007
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:8.935
Then Tails is running from USB drive "old" 0.363
And all tps features are active 1.930
When I write some files expected to persist 1.579
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.205
And all persistence configuration files have safe access rights 0.347
And all persistent directories from the old Tails version have safe access rights 2.498
And I take note of which tps features are available 0.507
And I shutdown Tails and wait for the computer to power off 4.193
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.556
After features/support/hooks.rb:326 0.136
After features/support/hooks.rb:100 0.008
Tags: @product
2:20.141
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.886
And I log in to a new session 16.555
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.476
And I plug USB drive "to_upgrade" 2.390
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.326
Then the running Tails is installed on USB drive "to_upgrade" 17.115
And I unplug USB drive "to_upgrade" 0.195
And I unplug USB drive "__internal" 0.194
After features/support/hooks.rb:326 3.841
After features/support/hooks.rb:100 0.000
Tags: @product
2:11.606
Before features/support/hooks.rb:269 0.009
Given a computer 0.220
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.832
Then all tps features from the old Tails version are active 1.388
And Tails is running from USB drive "to_upgrade" 0.291
And the boot device has safe access rights 3.160
And the expected persistent files created with the old Tails version are present in the filesystem 1.362
And all persistent directories from the old Tails version have safe access rights 2.349
After features/support/hooks.rb:326 0.901
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:9.176
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.571
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.403
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.111
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.272
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.450
When the network is plugged 0.041
And Tor is ready 21.564
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.010
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.986
Given I shutdown Tails and wait for the computer to power off 8.758
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.839
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.013
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.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.350
# 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.328
When the network is plugged 0.046
And Tor is ready 16.307
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.951
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.655
Given I shutdown Tails and wait for the computer to power off 4.326
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.092
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.769
And the file system changes introduced in version 6.3~testoverlayfs are present 0.418
And only the 6.3~testoverlayfs SquashFS delta is installed 0.081
# 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.329
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.256
When the network is plugged 0.041
And Tor is ready 17.220
Then the Upgrader considers the system as up-to-date 10.714
# 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.905
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.909
After features/support/hooks.rb:326 0.688
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
32.261
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.633
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.361
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.866
But a current signing key is available on our website 0.000
When the network is plugged 0.032
And Tor is ready 16.451
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.844
After features/support/hooks.rb:326 1.167
After features/support/hooks.rb:100 0.000