stleary/JSON-Java-unit-test

Issues

• Archive project and update update readme to reflect project merge

  #97 opened 4 years ago by johnjaylward
  1

• Consider partitioning tests for behavior, bug fixes, exceptions, etc

  #67 opened 6 years ago by stleary
  5

• Unit tests need better coverage of JSONWriter exceptions

  #56 opened 6 years ago by stleary
  1

• Code coverage should be included in the gradle build

  #38 opened 8 years ago by stleary
  1

• Code should be compatible with Java 1.6 if practical

  #40 opened 8 years ago by stleary
  1

• Is the tag 20160212 targeting JSON-Java/20160212?

  #41 opened 9 years ago by jinahya
  1

• Move files to maven-friendly directories

  #36 opened 9 years ago by stleary
  1

• Need a test for package and classloader

  #5 opened 9 years ago by stleary
  0

• Refactor test classes

  #4 opened 9 years ago by stleary
  0

• JSONObject and JSONArray input value conversion to object tests

  #8 opened 9 years ago by stleary
  0

• Add JsonPath support

  #15 opened 9 years ago by stleary
  2

• Investigate issues with changing only the JSONObject and JSONArray ctors

  #27 opened 9 years ago by stleary
  3

• Util should have only 1 public top level object comparison method.

  #3 opened 9 years ago by stleary
  1

• Document how XML.java and the "content" keyword work.

  #17 opened 9 years ago by stleary
  1

• IntegrateUnitTests into douglascrockford/JSON-java

  #20 opened 9 years ago by mdaehnert
  4

• Exception tests should check for actual exception string

  #9 opened 9 years ago by stleary
  1

• Do a more thorough review of original cdl test

  #1 opened 10 years ago by stleary
  0

• Update CDLTest to remove string tests as much as practical

  #2 opened 10 years ago by stleary
  0