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
inspiration from a presentation on fuzzing redux.
Each test harness (while (/**/) { try {/**/} catch(e) {/**/} }) should be able to create a minimal testcase from a generated errror. The output should be a string, so it can be written to stdout/stderr/a file.
testfunc.toString() is an attractive strategy for implementation, but seems brittle. I'm certain if the code gets minified f.toString will be unintelligible. I don't know how it will work with high-order functions. Writing each action of the array to replay as functions seems like a memory leak waiting to happen.
The easy way out is requiring each instance of Monkey to have a method that serializes each action.
Bonus points if you manage to eliminate unneccessaray left-padding.
The text was updated successfully, but these errors were encountered:
inspiration from a presentation on fuzzing redux.
Each test harness (
while (/**/) { try {/**/} catch(e) {/**/} }
) should be able to create a minimal testcase from a generated errror. The output should be a string, so it can be written to stdout/stderr/a file.testfunc.toString()
is an attractive strategy for implementation, but seems brittle. I'm certain if the code gets minifiedf.toString
will be unintelligible. I don't know how it will work with high-order functions. Writing each action of the array to replay as functions seems like a memory leak waiting to happen.The easy way out is requiring each instance of
Monkey
to have a method that serializes each action.Bonus points if you manage to eliminate unneccessaray left-padding.
The text was updated successfully, but these errors were encountered: