Project Number Date
test_Tails_ISO_devel 3206 22 Dec 2023, 12:31

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 16:52.359 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
1:24.304
Before features/support/hooks.rb:245 0.005
Given a computer 0.213
And I create a 7200 MiB disk named "old" 0.056
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 18.613
When I start Tails from USB drive "old" with network unplugged 1:0.628
Then the boot device has safe access rights 2.902
And Tails is running from USB drive "old" 0.297
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.047
And udev-watchdog is monitoring the correct device 0.254
And I unplug USB drive "old" 0.177
After features/support/hooks.rb:291 3.490
After features/support/hooks.rb:75 0.010
Tags: @product
1:57.585
Before features/support/hooks.rb:245 0.006
Given a computer 0.193
And I start Tails from USB drive "old" with network unplugged and I login 1:3.647
Then Tails is running from USB drive "old" 0.431
And I create a persistent partition 43.921
And I take note of which tps features are available 1.436
Then a Tails persistence partition exists on USB drive "old" 0.870
And I shutdown Tails and wait for the computer to power off 7.084
After features/support/hooks.rb:291 0.143
After features/support/hooks.rb:75 0.010
Tags: @product
2:23.536
Before features/support/hooks.rb:245 0.005
Given a computer 0.178
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:56.074
Then Tails is running from USB drive "old" 0.355
And all tps features are active 1.961
When I write some files expected to persist 1.812
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.241
And all persistence configuration files have safe access rights 0.637
And all persistent directories from the old Tails version have safe access rights 2.619
And I take note of which tps features are available 0.724
And I shutdown Tails and wait for the computer to power off 3.057
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.872
After features/support/hooks.rb:291 0.129
After features/support/hooks.rb:75 0.008
Tags: @product
2:33.726
Before features/support/hooks.rb:245 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.120
And I log in to a new session 15.082
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.198
And I plug USB drive "to_upgrade" 2.416
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:51.763
Then the running Tails is installed on USB drive "to_upgrade" 12.770
And I unplug USB drive "to_upgrade" 0.198
And I unplug USB drive "__internal" 0.176
After features/support/hooks.rb:291 3.786
After features/support/hooks.rb:75 0.000
Tags: @product
2:15.611
Before features/support/hooks.rb:245 0.014
Given a computer 0.216
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.452
Then all tps features from the old Tails version are active 1.660
And Tails is running from USB drive "to_upgrade" 0.348
And the boot device has safe access rights 3.542
And the expected persistent files created with the old Tails version are present in the filesystem 1.492
And all persistent directories from the old Tails version have safe access rights 2.898
After features/support/hooks.rb:291 0.669
After features/support/hooks.rb:75 0.013
Tags: @product @automatic_upgrade
5:48.814
Before features/support/hooks.rb:245 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.105
And no SquashFS delta is installed 0.125
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.485
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.094
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.420
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.644
When the network is plugged 0.038
And Tor is ready 16.342
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.719
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.913
Given I shutdown Tails and wait for the computer to power off 7.293
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.210
Then Tails is running version 2.2~testoverlayfsng 0.085
And all tps features are active 2.184
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.397
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.299
# We'll really install Tails_amd64_2.0~testoverlayfsng_to_2.3~testoverlayfsng.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 2.1~testoverlayfsng was initially installed 0.293
When the network is plugged 0.052
And Tor is ready 15.473
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.663
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.150
Given I shutdown Tails and wait for the computer to power off 4.355
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:43.374
Then Tails is running version 2.3~testoverlayfsng 0.146
And all tps features are active 1.956
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.589
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.063
# 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.288
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.391
When the network is plugged 0.045
And Tor is ready 17.092
Then the Upgrader considers the system as up-to-date 0.319
# 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 26.692
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.440
After features/support/hooks.rb:291 0.758
After features/support/hooks.rb:75 0.019
Tags: @product @automatic_upgrade
28.779
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.026
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.336
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.079
And the signing key used by the Upgrader is outdated 0.750
But a current signing key is available on our website 0.000
When the network is plugged 0.031
And Tor is ready 15.864
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.690
After features/support/hooks.rb:291 0.775
After features/support/hooks.rb:75 0.000