-
Notifications
You must be signed in to change notification settings - Fork 12
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
Update current test cases #8
Comments
@kxepal Need some details here of the work -- do you mean the spec itself should provide more example/sample files or a certain impl on a certain platform needs more test cases? |
@thebuzzmedia more examples with valid and malformed UBJSON data. For example:
and etc. to help developers synchronise libraries behaviour, clearly define invalid cases and suggest common ways to react on them and so on. Current ones are good and even suitable for benchmarking, but they covers only positive scenarios while there are a lot of negative ones. |
Absolutely agree, thank you for clarifying. Riyad On Sun, Apr 14, 2013 at 11:29 AM, Alexander Shorin <notifications@github.com
|
Reviving this old issue. The test cases provided are clearly not following the current specifications. I would be good to move those files to a directory specifying the draft version they follow. |
You are right those examples are all Draft 8. I handed ownership to Steven On Thu, Oct 13, 2016 at 12:26 PM, Dorian notifications@github.com wrote:
|
subj.
The text was updated successfully, but these errors were encountered: