Project Number Date
test_Tails_ISO_stable 5284 22 Nov 2024, 08:41

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:6.902 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.126
Before features/support/hooks.rb:269 0.006
Given a computer 0.211
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 31.577
When I start Tails from USB drive "old" with network unplugged 1:31.256
Then the boot device has safe access rights 3.004
And Tails is running from USB drive "old" 0.327
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.101
And udev-watchdog is monitoring the correct device 0.291
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:326 7.296
After features/support/hooks.rb:100 0.008
Tags: @product
2:15.679
Before features/support/hooks.rb:269 0.004
Given a computer 0.214
And I start Tails from USB drive "old" with network unplugged and I login 1:32.792
Then Tails is running from USB drive "old" 0.411
And I create a persistent partition 31.387
And I take note of which tps features are available 1.584
Then a Tails persistence partition exists on USB drive "old" 0.891
And I shutdown Tails and wait for the computer to power off 8.397
After features/support/hooks.rb:326 0.175
After features/support/hooks.rb:100 0.009
Tags: @product
2:59.043
Before features/support/hooks.rb:269 0.006
Given a computer 0.228
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.222
Then Tails is running from USB drive "old" 0.328
And all tps features are active 2.090
When I write some files expected to persist 2.205
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.244
And all persistence configuration files have safe access rights 0.474
And all persistent directories from the old Tails version have safe access rights 2.624
And I take note of which tps features are available 0.478
And I shutdown Tails and wait for the computer to power off 6.421
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.724
After features/support/hooks.rb:326 0.185
After features/support/hooks.rb:100 0.010
Tags: @product
2:38.093
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 12.119
And I log in to a new session 23.380
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.987
And I plug USB drive "to_upgrade" 2.461
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.698
Then the running Tails is installed on USB drive "to_upgrade" 21.013
And I unplug USB drive "to_upgrade" 0.199
And I unplug USB drive "__internal" 0.232
After features/support/hooks.rb:326 3.519
After features/support/hooks.rb:100 0.000
Tags: @product
2:28.900
Before features/support/hooks.rb:269 0.004
Given a computer 0.180
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:19.025
Then all tps features from the old Tails version are active 1.799
And Tails is running from USB drive "to_upgrade" 0.420
And the boot device has safe access rights 3.466
And the expected persistent files created with the old Tails version are present in the filesystem 1.447
And all persistent directories from the old Tails version have safe access rights 2.560
After features/support/hooks.rb:326 1.057
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:50.238
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 13.747
And no SquashFS delta is installed 0.202
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.444
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.289
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.434
When the network is plugged 0.096
And Tor is ready 24.413
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.900
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.927
Given I shutdown Tails and wait for the computer to power off 11.788
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.780
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.389
And the file system changes introduced in version 6.2~testoverlayfs are present 0.340
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.333
# 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.297
When the network is plugged 0.070
And Tor is ready 21.781
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.739
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.466
Given I shutdown Tails and wait for the computer to power off 4.369
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.044
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.340
And the file system changes introduced in version 6.3~testoverlayfs are present 0.465
And only the 6.3~testoverlayfs SquashFS delta is installed 0.084
# 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.339
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.343
When the network is plugged 0.063
And Tor is ready 15.253
Then the Upgrader considers the system as up-to-date 10.749
# 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 16.462
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.118
After features/support/hooks.rb:326 1.270
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
46.820
Before features/support/hooks.rb:269 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.916
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.615
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 0.898
But a current signing key is available on our website 0.000
When the network is plugged 0.077
And Tor is ready 22.791
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.464
After features/support/hooks.rb:326 0.687
After features/support/hooks.rb:100 0.000