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
{{ message }}
This repository has been archived by the owner on Oct 9, 2019. It is now read-only.
When testing with fuzzers for a large/complex model with many nested models I encountered issues with test performance. My tests would either take a very long time to complete or threw an out of memory exception. To prevent encountering the out of memory exception I reduced the amount of fuzzers used per test by decomposing my tests into smaller components, which also increased test performance. Documentation on the limitations of nested fuzzers would be helpful to people in the future who experience the same problems as myself.
The text was updated successfully, but these errors were encountered:
Works, but very slow: a 100 item run takes 50-65s. Printing timing info revealed that
only about 1/3rd of the time is spent running the test validation. The rest is presumably
the fuzzer. The shrinker never seems to come into play (which makes sense since all
tests pass). This seems to be a known issue with fuzzers:
elm-community/elm-test#237
With that said, I'll put this branch on hold. The code is as-is, as in not in a state
of which I'm particularly proud of but whatever :)
When testing with fuzzers for a large/complex model with many nested models I encountered issues with test performance. My tests would either take a very long time to complete or threw an out of memory exception. To prevent encountering the out of memory exception I reduced the amount of fuzzers used per test by decomposing my tests into smaller components, which also increased test performance. Documentation on the limitations of nested fuzzers would be helpful to people in the future who experience the same problems as myself.
The text was updated successfully, but these errors were encountered: