-
Notifications
You must be signed in to change notification settings - Fork 9
Description
The current speed tests really only test quoted strings, it should test all data types.
Also some validity testing of numbers (ie does it treat 1.2.3 as a number or a string?),
hex numbers
dates (ISO 8601)
booleans
Test handling of escape characters, unicode escapes
Use specific test files that are never written to so that each library is parsing the same thing, rather than a file it generated itself.
Add more methods to ILib to enable generating more complex documents with differnent data structures and data types. That might be more difficult to achieve due to the differences in the libs. Perhaps rather than calling Lib.Add it should just be Lib.BuildDocA Lib.BuildDocB and have each lib build the same document - although how you would validate that I don't know.
Handle errors in the tests - if a library raises and exception then the report should not report timing and just say ERROR - it took me a while to realise my parser was failing the load test because I didn't read the earlier output.
The timing isn't very accurate, but these tests do give a reasonable indication.
There is probably more I could think of but it is all a lot of work so I won't be upset if you ignore my suggestions ;)