>> Is there any value in them as regression tests (maybe with more
>> elaborate inputs and/or longer runtimes)?
Antoine> You mean to check behaviour or to check for performance
Antoine> regressions?
Both. Semantic regressions, and secondarily, performance regressions.
I can understand the need to stabilize the code and inputs for measuring
performance. As bad a benchmark as pystone is, one of its saving graces is
that it hasn't changed in so long.
When looking for semantic problems I can see that you would add new packages
to the suite where they expose problems, just as we do today for unit tests.
Skip
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4