-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What about adding much more test cases? #900
Comments
If you want to see use-case for benchmark: https://github.com/samchon/typescript-json/blob/master/benchmark/features/benchmark_is.ts |
I am open to having more tests, but we need to be mindful of total run time. If we have too many or too slow ones then it'll be taking a long time, and we can even eventually run out of CI time limit 😁 But having more different tests, I think is a good idea overall. Just need to understand what we are targeting and what are usually the slow parts. |
Validation failures are also one less-benchmarked case. Their performance also becomes relevant in cases like |
Wrote another issue with a little bit different idea -> #1025 |
https://github.com/samchon/typescript-json/tree/master/test/structures
I'm developing a runtime type checker (validator) library, and have prepared lots of test cases, for hardcore validation.
How about
typescript-runtime-type-benchmarks
to adapt such test cases?They may be useful.
The text was updated successfully, but these errors were encountered: