You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We'll want to periodically call view methods to increase coverage. Additionally, assertion testing supports config-driven options to enable assert testing of view methods, but the FuzzerWorker only produces CallSequences with calls targeting state changing methods right now, so it's never hit.
Requirements:
Record view functions separately, but alongside the existing stateChangingMethods (see the updateStateChangingMethods method)
Add a really low probability of sourcing a target method from it (instead of stateChangingMethods) at the top of the generateFuzzedCall method.
Ensure the corpus.UpdateCorpusAndCoverageMaps method checks if the last call was to a view method. If it was, do not record the call sequence in the corpus at that step, as it's not a coverage-increasing sequence we'd be interested in recording, as it was not state changing.
The text was updated successfully, but these errors were encountered:
We'll want to periodically call view methods to increase coverage. Additionally, assertion testing supports config-driven options to enable assert testing of view methods, but the
FuzzerWorker
only producesCallSequence
s with calls targeting state changing methods right now, so it's never hit.Requirements:
stateChangingMethods
(see theupdateStateChangingMethods
method)stateChangingMethods
) at the top of thegenerateFuzzedCall
method.corpus.UpdateCorpusAndCoverageMaps
method checks if the last call was to a view method. If it was, do not record the call sequence in the corpus at that step, as it's not a coverage-increasing sequence we'd be interested in recording, as it was not state changing.The text was updated successfully, but these errors were encountered: