# JSON-Java-unit-test
Unit tests to validate the JSON-Java GitHub project code (https://github.com/douglascrockford/JSON-java).
Test harness: http://junit.org
Coverage: http://www.eclemma.org/
Eclipse is the recommended development environment.
Run individual tests or JunitTestSuite using *EclEmma Coverage*, or execute the TestRunner application directly.
Test filenames should consist of the name of the module being tested, with the suffix "Test".
For example, Cookie.java is tested by CookieTest.java.
When adding a new unit test, don't forget to update JunitTestSuite.java.
The fundamental issues with JSON-Java testing are:
* JSONObjects are unordered, making simple string comparison ineffective.
* Comparisons via **equals()** is not currently supported. Neither JSONArray nor JSONObject overrride hashCode() or equals(), so comparison defaults to the Object equals(), which is not useful.
* Access to the JSONArray and JSONObject internal containers for comparison is not currently available.
* JSONObject sometimes wraps entries in quotes, other times does not, complicating comparisons.
When you start working on a test, add the empty file to the repository and update the readme, so that others will know that test is taken.
A unit test is considered complete when the coverage is >= 90% as measured by EclEmma.
| Test file name | Coverage | Comments |
| ------------- | ------------- | ---- |
| Total coverage | 58.4% | | |
| | | |
| CDL.java | 94.8% | Completed |
| Cookie.java | 97.5% | Completed |
| CookieList.java |96.5% | Completed |
| HTTP.java | 98.7%| Completed |
| HTTPTokener.java |93.2% |Completed |
| JSONArray.java |18.3% | |
| JSONException.java | 26.7% | |
| JSONML.java | 83.2%| completed |
| JSONObject | 24.9% | | in progress |
| JSONObject.Null | 75.0% | | |
| JSONStringer.java | 93.8%| Completed |
| JSONTokener.java | 72.1% | |
| JSONWriter.java | 88.9% | Completed |
| Property.java | 94.8% | Completed |
| XML.java | 85.1% | Completed |
| XMLTokener.java| 82.7%| Completed |