Project Number Date
test_Tails_ISO_stable 5028 14 Aug 2024, 08:39

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:7.716 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:9.331
Before features/support/hooks.rb:269 0.008
Given a computer 0.217
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 32.050
When I start Tails from USB drive "old" with network unplugged 1:31.848
Then the boot device has safe access rights 3.103
And Tails is running from USB drive "old" 0.311
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.289
And I unplug USB drive "old" 0.238
After features/support/hooks.rb:326 7.053
After features/support/hooks.rb:100 0.009
Tags: @product
2:10.217
Before features/support/hooks.rb:269 0.005
Given a computer 0.210
And I start Tails from USB drive "old" with network unplugged and I login 1:24.586
Then Tails is running from USB drive "old" 0.390
And I create a persistent partition 31.593
And I take note of which tps features are available 1.914
Then a Tails persistence partition exists on USB drive "old" 0.864
And I shutdown Tails and wait for the computer to power off 10.656
After features/support/hooks.rb:326 0.217
After features/support/hooks.rb:100 0.020
Tags: @product
2:59.012
Before features/support/hooks.rb:269 0.010
Given a computer 0.262
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.018
Then Tails is running from USB drive "old" 0.364
And all tps features are active 2.876
When I write some files expected to persist 2.379
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.373
And all persistence configuration files have safe access rights 0.484
And all persistent directories from the old Tails version have safe access rights 2.916
And I take note of which tps features are available 1.095
And I shutdown Tails and wait for the computer to power off 4.159
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.081
After features/support/hooks.rb:326 0.142
After features/support/hooks.rb:100 0.011
Tags: @product
2:37.740
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.333
And I log in to a new session 22.812
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.856
And I plug USB drive "to_upgrade" 2.652
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.484
Then the running Tails is installed on USB drive "to_upgrade" 19.085
And I unplug USB drive "to_upgrade" 0.235
And I unplug USB drive "__internal" 0.279
After features/support/hooks.rb:326 3.720
After features/support/hooks.rb:100 0.000
Tags: @product
2:25.633
Before features/support/hooks.rb:269 0.009
Given a computer 0.273
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:15.663
Then all tps features from the old Tails version are active 1.790
And Tails is running from USB drive "to_upgrade" 0.418
And the boot device has safe access rights 3.474
And the expected persistent files created with the old Tails version are present in the filesystem 1.411
And all persistent directories from the old Tails version have safe access rights 2.601
After features/support/hooks.rb:326 0.934
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
7:4.406
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 32.932
And no SquashFS delta is installed 0.201
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.302
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.343
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.440
When the network is plugged 0.106
And Tor is ready 18.761
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.010
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.281
Given I shutdown Tails and wait for the computer to power off 16.061
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.414
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.506
And the file system changes introduced in version 6.2~testoverlayfs are present 0.334
And only the 6.2~testoverlayfs SquashFS delta is installed 0.089
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.349
# 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.281
When the network is plugged 0.089
And Tor is ready 18.175
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.603
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.747
Given I shutdown Tails and wait for the computer to power off 4.784
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.302
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.354
And the file system changes introduced in version 6.3~testoverlayfs are present 0.752
And only the 6.3~testoverlayfs SquashFS delta is installed 0.101
# 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.370
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.350
When the network is plugged 0.080
And Tor is ready 17.360
Then the Upgrader considers the system as up-to-date 0.395
# 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.005
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.430
After features/support/hooks.rb:326 1.079
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
41.373
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.717
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.353
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.954
But a current signing key is available on our website 0.000
When the network is plugged 0.068
And Tor is ready 20.202
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.018
After features/support/hooks.rb:326 0.944
After features/support/hooks.rb:100 0.000