QLS: statically enable/disable fault injection depending on the SUT #534
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Builds on top of #533.
This is a WIP, so not ready for review yet.
Faults can only be injected into a mocked
HasFS
, but not all the SUTs we test use a mockedHasFS
. If the SUT does not make use of a mockedHasFS
then the result of fault injection will always beInjectFaultAccidentalSuccess
. This PR adds some boilerplate for statically enabling/disabling fault injection depending on the SUT.Fault injection is then enabled for the following SUTs:
IO
using a mockedHasFS
IOSim
using a mockedHasFS
Fault injection is then disabled for the following SUTs:
HasFS
IO
using the realHasFS
: it uses the real file system