Project Number Date
test_Tails_ISO_stable 5244 02 Nov 2024, 12:51

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 22:40.060 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:31.359
Before features/support/hooks.rb:269 0.005
Given a computer 0.207
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 32.280
When I start Tails from USB drive "old" with network unplugged 1:53.156
Then the boot device has safe access rights 3.565
And Tails is running from USB drive "old" 0.346
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.105
And udev-watchdog is monitoring the correct device 0.295
And I unplug USB drive "old" 0.237
After features/support/hooks.rb:326 3.533
After features/support/hooks.rb:100 0.010
Tags: @product
2:12.633
Before features/support/hooks.rb:269 0.006
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login 1:23.656
Then Tails is running from USB drive "old" 0.379
And I create a persistent partition 36.726
And I take note of which tps features are available 1.796
Then a Tails persistence partition exists on USB drive "old" 0.903
And I shutdown Tails and wait for the computer to power off 8.982
After features/support/hooks.rb:326 0.179
After features/support/hooks.rb:100 0.010
Tags: @product
3:1.317
Before features/support/hooks.rb:269 0.007
Given a computer 0.225
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.094
Then Tails is running from USB drive "old" 0.964
And all tps features are active 2.071
When I write some files expected to persist 3.835
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 1.028
And all persistence configuration files have safe access rights 0.447
And all persistent directories from the old Tails version have safe access rights 2.587
And I take note of which tps features are available 0.428
And I shutdown Tails and wait for the computer to power off 4.434
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.199
After features/support/hooks.rb:326 0.153
After features/support/hooks.rb:100 0.008
Tags: @product
2:42.899
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 16.363
And I log in to a new session 22.930
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.159
And I plug USB drive "to_upgrade" 2.680
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.119
Then the running Tails is installed on USB drive "to_upgrade" 22.103
And I unplug USB drive "to_upgrade" 0.244
And I unplug USB drive "__internal" 0.298
After features/support/hooks.rb:326 2.259
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.110
Before features/support/hooks.rb:269 0.006
Given a computer 0.218
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.193
Then all tps features from the old Tails version are active 1.942
And Tails is running from USB drive "to_upgrade" 0.418
And the boot device has safe access rights 3.932
And the expected persistent files created with the old Tails version are present in the filesystem 1.656
And all persistent directories from the old Tails version have safe access rights 2.749
After features/support/hooks.rb:326 0.840
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
9:5.818
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 18.333
And no SquashFS delta is installed 0.090
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.379
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.314
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.481
When the network is plugged 0.068
And Tor is ready 21.788
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.416
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.485
Given I shutdown Tails and wait for the computer to power off 1:22.474
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:19.542
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.502
And the file system changes introduced in version 6.2~testoverlayfs are present 0.356
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.421
# 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.402
When the network is plugged 0.077
And Tor is ready 21.979
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.288
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.278
Given I shutdown Tails and wait for the computer to power off 1:4.118
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.764
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.009
And the file system changes introduced in version 6.3~testoverlayfs are present 0.477
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.352
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.296
When the network is plugged 0.081
And Tor is ready 20.538
Then the Upgrader considers the system as up-to-date 0.326
# 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.915
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.009
After features/support/hooks.rb:326 0.740
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
41.921
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 12.906
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.705
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.081
And the signing key used by the Upgrader is outdated 0.773
But a current signing key is available on our website 0.000
When the network is plugged 0.106
And Tor is ready 20.125
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.222
After features/support/hooks.rb:326 0.862
After features/support/hooks.rb:100 0.000