Project Number Date
test_Tails_ISO_devel 3433 18 Jun 2024, 23:10

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 21:7.513 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:19.488
Before features/support/hooks.rb:269 0.008
Given a computer 0.239
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 34.167
When I start Tails from USB drive "old" with network unplugged 1:39.715
Then the boot device has safe access rights 3.170
And Tails is running from USB drive "old" 0.363
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.134
And udev-watchdog is monitoring the correct device 0.345
And I unplug USB drive "old" 0.180
After features/support/hooks.rb:326 3.545
After features/support/hooks.rb:100 0.022
Tags: @product
2:6.367
Before features/support/hooks.rb:269 0.010
Given a computer 0.231
And I start Tails from USB drive "old" with network unplugged and I login 1:24.217
Then Tails is running from USB drive "old" 0.371
And I create a persistent partition 30.627
And I take note of which tps features are available 1.358
Then a Tails persistence partition exists on USB drive "old" 0.890
And I shutdown Tails and wait for the computer to power off 8.670
After features/support/hooks.rb:326 0.214
After features/support/hooks.rb:100 0.009
Tags: @product
3:0.428
Before features/support/hooks.rb:269 0.006
Given a computer 0.236
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.328
Then Tails is running from USB drive "old" 0.331
And all tps features are active 2.037
When I write some files expected to persist 1.741
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.213
And all persistence configuration files have safe access rights 0.355
And all persistent directories from the old Tails version have safe access rights 2.861
And I take note of which tps features are available 0.510
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" 25.361
After features/support/hooks.rb:326 0.107
After features/support/hooks.rb:100 0.010
Tags: @product
2:31.583
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.004
And I log in to a new session 18.390
And I clone USB drive "old" to a new USB drive "to_upgrade" 3.205
And I plug USB drive "to_upgrade" 2.424
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.476
Then the running Tails is installed on USB drive "to_upgrade" 16.680
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.198
After features/support/hooks.rb:326 1.031
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.574
Before features/support/hooks.rb:269 0.009
Given a computer 0.387
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.365
Then all tps features from the old Tails version are active 1.978
And Tails is running from USB drive "to_upgrade" 0.414
And the boot device has safe access rights 3.407
And the expected persistent files created with the old Tails version are present in the filesystem 1.486
And all persistent directories from the old Tails version have safe access rights 2.534
After features/support/hooks.rb:326 0.647
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
8:12.278
Before features/support/hooks.rb:269 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 32.680
And no SquashFS delta is installed 0.525
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.340
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.318
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.422
When the network is plugged 0.210
And Tor is ready 22.026
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.252
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.126
Given I shutdown Tails and wait for the computer to power off 10.834
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.930
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.249
And the file system changes introduced in version 6.2~testoverlayfs are present 0.367
And only the 6.2~testoverlayfs SquashFS delta is installed 0.101
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.321
# 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.309
When the network is plugged 0.041
And Tor is ready 16.687
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.570
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.547
Given I shutdown Tails and wait for the computer to power off 1:1.634
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:24.589
Then Tails is running version 6.3~testoverlayfs 0.020
And all tps features are active 3.061
And the file system changes introduced in version 6.3~testoverlayfs are present 0.557
And only the 6.3~testoverlayfs SquashFS delta is installed 0.090
# 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.361
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.360
When the network is plugged 0.047
And Tor is ready 22.461
Then the Upgrader considers the system as up-to-date 0.368
# 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.509
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.270
After features/support/hooks.rb:326 0.782
After features/support/hooks.rb:100 0.029
Tags: @product @automatic_upgrade
40.791
Before features/support/hooks.rb:269 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.049
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.092
And the signing key used by the Upgrader is outdated 0.966
But a current signing key is available on our website 0.000
When the network is plugged 0.070
And Tor is ready 21.377
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.867
After features/support/hooks.rb:326 0.776
After features/support/hooks.rb:100 0.000