Closed dtaillard closed 9 years ago
Thanks, will review and respond soon. Quick impression, looks good.
Are you sure this is the version you wanted to commit? It does not seem to compile. Also there are a few methods where some of the test functionality was removed. For example, in shouldHandleToString(), the intent was to confirm that the XML.toString() method worked correctly. In the new code, XML.toString() is never called.
Well, I messed up there. I'll fix it. I think that a build system (like gradle) would make it much easier to build the project, rather than trying to add the jUnit dependency manually. Why are the source files not in the org.json.junit.package
as declared with the package
statement at the top of each source file? Could I add create the actual package so that it compiles?
I use Eclipse. Would be interested in seeing your gradle build scripts when you are done. Regarding the source files, I think you are asking why they are not found in a directory structure that matches the package declaration. That will probably be fixed when I post the test code to the Maven central repository, in a future release.
My latest commit fixes the errors, and should bring that functionality back.
Will get to this as soon as I can - been having a busy week.
Can't be accepted as is. Syntax error:at line 48, compareJSONObjectToString() is not a method.
Some tests throw exceptions:or fail
Let me mavenize both probjects and provide instructions on how to run the unit tests, and we can work from there. Will have something ready for you soon.
Just let me know when you can provide instructions. :+1:
Will do, currently caught up in sprint catch up work. Seems to happen towards the end of every sprint.
No rush.
This branch introduces changes that should finish unit tests for
XML.toJSONObjectReader()
. I have changed many of the tests to start usingcompareStringToJSONObject()
,compareReaderToJSONObject()
, andcompareFileToJSONObject()
.Tell me what you think.