Project Number Date
test_Tails_ISO_stable 5286 23 Nov 2024, 09:07

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:42.338 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:12.435
Before features/support/hooks.rb:269 0.005
Given a computer 0.211
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.083
And I write an old version of the Tails USB image to disk "old" 35.757
When I start Tails from USB drive "old" with network unplugged 1:31.057
Then the boot device has safe access rights 3.251
And Tails is running from USB drive "old" 0.334
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.312
And I unplug USB drive "old" 0.212
After features/support/hooks.rb:326 3.629
After features/support/hooks.rb:100 0.014
Tags: @product
2:14.526
Before features/support/hooks.rb:269 0.004
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login 1:31.587
Then Tails is running from USB drive "old" 0.396
And I create a persistent partition 30.713
And I take note of which tps features are available 2.220
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.526
After features/support/hooks.rb:326 0.196
After features/support/hooks.rb:100 0.008
Tags: @product
3:1.357
Before features/support/hooks.rb:269 0.005
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.832
Then Tails is running from USB drive "old" 1.198
And all tps features are active 2.166
When I write some files expected to persist 3.872
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.320
And all persistence configuration files have safe access rights 0.459
And all persistent directories from the old Tails version have safe access rights 2.672
And I take note of which tps features are available 0.707
And I shutdown Tails and wait for the computer to power off 4.215
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.714
After features/support/hooks.rb:326 0.136
After features/support/hooks.rb:100 0.011
Tags: @product
2:36.612
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.138
And I log in to a new session 20.772
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.132
And I plug USB drive "to_upgrade" 2.599
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.099
Then the running Tails is installed on USB drive "to_upgrade" 23.433
And I unplug USB drive "to_upgrade" 0.209
And I unplug USB drive "__internal" 0.226
After features/support/hooks.rb:326 7.079
After features/support/hooks.rb:100 0.000
Tags: @product
2:23.807
Before features/support/hooks.rb:269 0.006
Given a computer 0.201
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.779
Then all tps features from the old Tails version are active 1.996
And Tails is running from USB drive "to_upgrade" 0.331
And the boot device has safe access rights 3.250
And the expected persistent files created with the old Tails version are present in the filesystem 1.587
And all persistent directories from the old Tails version have safe access rights 2.659
After features/support/hooks.rb:326 0.962
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:34.200
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 36.772
And no SquashFS delta is installed 0.101
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.366
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.315
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.433
When the network is plugged 0.179
And Tor is ready 26.652
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.877
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.972
Given I shutdown Tails and wait for the computer to power off 11.153
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:28.387
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.704
And the file system changes introduced in version 6.2~testoverlayfs are present 0.405
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.347
# 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.299
When the network is plugged 0.075
And Tor is ready 15.683
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.806
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.068
Given I shutdown Tails and wait for the computer to power off 4.307
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.572
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 6.341
And the file system changes introduced in version 6.3~testoverlayfs are present 0.458
And only the 6.3~testoverlayfs SquashFS delta is installed 0.086
# 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.345
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.329
When the network is plugged 0.375
And Tor is ready 19.269
Then the Upgrader considers the system as up-to-date 0.325
# 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 14.913
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.115
After features/support/hooks.rb:326 0.734
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
39.399
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 10.814
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.886
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.080
And the signing key used by the Upgrader is outdated 1.252
But a current signing key is available on our website 0.000
When the network is plugged 0.081
And Tor is ready 19.435
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.848
After features/support/hooks.rb:326 0.756
After features/support/hooks.rb:100 0.000