{"push_id":1433383660,"size":9,"distinct_size":7,"ref":"refs/heads/scalacheck","head":"6c1315311d2f557ee4f3357d7f38d97c751ce4e3","before":"1e398f79c96baf9189f247049d52cd8c2a28d4e6","commits":[{"sha":"2fd69b22f791f9f41f6cf2c365b7abe8dc80fee2","author":{"name":"Seth Tisue","email":"502bdf57888b0e86dbf5fd8a5f3627a6559f21a9@tisue.net"},"message":"upgrade to sbt 0.13.13\n\nthis is a good thing in general, to be on a modern sbt version.\n\nbut also, in the Scala community build some weird dbuild issue\nI don't understand is causing scala-xml to be built with 0.13.8\ninstead of being overridden by dbuild to 0.13.13 like all the\nother projects. rather than mess with it, let's just upgrade.","distinct":false,"url":"https://api.github.com/repos/ashawley/scala-xml/commits/2fd69b22f791f9f41f6cf2c365b7abe8dc80fee2"},{"sha":"42163d494b35f93f9d817e6f38675880514c904a","author":{"name":"Seth Tisue","email":"502bdf57888b0e86dbf5fd8a5f3627a6559f21a9@tisue.net"},"message":"Merge pull request #124 from SethTisue/sbt-0.13.13\n\nupgrade to sbt 0.13.13","distinct":false,"url":"https://api.github.com/repos/ashawley/scala-xml/commits/42163d494b35f93f9d817e6f38675880514c904a"},{"sha":"57f0f08965d1a3de88cba01a3d2b5a79375a0cf5","author":{"name":"Aaron S. Hawley","email":"33bea6435d7defc0d2f5803f647c8432a437ec2e@gmail.com"},"message":"Add ScalaCheck to build.sbt","distinct":true,"url":"https://api.github.com/repos/ashawley/scala-xml/commits/57f0f08965d1a3de88cba01a3d2b5a79375a0cf5"},{"sha":"ebeee115230b584d9d1d2f4de86f636d8507ee93","author":{"name":"Aaron S. Hawley","email":"33bea6435d7defc0d2f5803f647c8432a437ec2e@gmail.com"},"message":"Add ScalaCheck specs to test suite\n\nAdds 26 specifications in ScalaCheck, with 154 properties, of 18 are\nproofs by example, and the rest are 136 tests using randomly-generated\nvalues.  ScalaCheck requires at least 100 generated tests to pass, by\ndefault.  So that gives 13,618 new tests!\n\nThe suite should be a real benefit for future maintenance endeavors,\nrewrites, documentation, or finishing a Scala-based parser to avoid\ndepending on the the Xerces/SAX Java library.\n\nThese integrate well with the existing suite of JUnit 4 tests.  If you\nwant to run both the ScalaCheck and JUnit tests from SBT,\n\n> test\n...\n[info] Passed: Total 145, Failed 0, Errors 0, Passed 145\n[success] Total time: 43 s, completed Sep 30, 2016 2:19:56 PM\n\nIf you want to run a single spec,\n\n> testOnly scala.xml.XMLSpec\n> testOnly scala.xml.XMLSpec\n[info] + XML.write: OK, passed 100 tests.\n[info] Passed: Total 1, Failed 0, Errors 0, Passed 1\n[success] Total time: 3 s, completed Sep 30, 2016 2:20:28 PM\n\nIf you want to run all the ScalaCheck specs,\n\n> testOnly *Spec\n...\n[info] Passed: Total 26, Failed 0, Errors 0, Passed 26\n[success] Total time: 30 s, completed Sep 30, 2016 2:22:58 PM\n\nIf you want to run the specs under a namespace,\n\n> testOnly scala.xml.dtd.*Spec\n...\n[info] + dtd.DTD.toString: OK, passed 100 tests.\n[info] + dtd.DocType.new(name): OK, passed 100 tests.\n[info] + dtd.DocType.new(name, extId, intSubset): OK, passed 100 tests.\n[info] + dtd.DocType.new(name, extId, emptyInt): OK, passed 100 tests.\n[info] + dtd.DocType.toString: OK, passed 100 tests.\n[info] Passed: Total 4, Failed 0, Errors 0, Passed 4\n[success] Total time: 6 s, completed Sep 30, 2016 3:14:05 PM\n\nIf you want to generate 1000 tests instead of 100,\n\n> testOnly *Spec -- -s 1000\n...\n[info] Passed: Total 26, Failed 0, Errors 0, Passed 26\n[success] Total time: 217 s, completed Sep 30, 2016 2:27:31 PM\n\nIf you want to generate 10 tests, instead of 100,\n\n> testOnly *Spec -- -s 10\n...\n[info] Passed: Total 26, Failed 0, Errors 0, Passed 26\n[success] Total time: 10 s, completed Sep 30, 2016 2:23:49 PM\n\nIf you want to generate full back traces on errors and display the elapsed time\nfor each property,\n\n> testOnly *Spec -- -verbosity 2\n...\n[info] + parsing.XhtmlParser.initialize: OK, passed 100 tests.\n[info] Elapsed time: 0.046 sec\n[info] + parsing.XhtmlParser.prolog: OK, passed 100 tests.\n[info] Elapsed time: 0.022 sec\n[info] + parsing.XhtmlParser.document: OK, passed 100 tests.\n[info] Elapsed time: 0.015 sec\n[info] Passed: Total 26, Failed 0, Errors 0, Passed 26\n[success] Total time: 30 s, completed Sep 30, 2016 2:29:24 PM\n\nThe default verbosity is 0,\n\n> testOnly *Spec -- -verbosity 0\n...\n[info] + parsing.XhtmlParser.initialize: OK, passed 100 tests.\n[info] + parsing.XhtmlParser.prolog: OK, passed 100 tests.\n[info] + parsing.XhtmlParser.document: OK, passed 100 tests.\n[info] Passed: Total 26, Failed 0, Errors 0, Passed 26\n[success] Total time: 26 s, completed Sep 30, 2016 2:30:26 PM\n\nTo run only the failed tests,\n\n> testQuick\n[info] Passed: Total 0, Failed 0, Errors 0, Passed 0\n[info] No tests to run for test:testQuick\n[success] Total time: 1 s, completed Sep 30, 2016 2:32:50 PM\n\nCurrently, these tests in ScalaCheck will cover only 25% of the source\ncode, and 20% of branches.\n\nNot surprisingly, there are some defects in scala-xml for certain\ntypes and classes.  I am forced to comment out and disable those tests\nand generators so that the suite passes.  Those issues should be taken\nup separately and in subsequent pull requests.  When those tests and\ngenerators are re-enabled for those types, the code coverage would\nmost likely increase.\n\nThere are no shrink heuristics defined written to help ScalaCheck\nidentify the minimum value to falsify a property of an XML string or\ndata structure.  This will be a nice to have, but was too advanced for\nme to take on at this time.\n\nRight now, the generators equally weight the Node types among those\nthat are allowed.  It would probably be worthwhile to have the\nfrequencies be more realistic.  For example, have a a greater emphasis\non Elem and EntityRef elements over Comment, ProcInstr, nulls,\nempty strings and empty lists.  The frequencies should be closer in\nline with what a typical XML file would be, but also more broadly\ncover the code and sooner using fewer generated values.\n\nSimilarly, there is not an appropriate sizing for lists.  Presently,\nScalaCheck randomly selects a number, and then the generators I wrote\nwill try to approach termination by recursively halving and\nsquare-rooting at each level of descent.","distinct":true,"url":"https://api.github.com/repos/ashawley/scala-xml/commits/ebeee115230b584d9d1d2f4de86f636d8507ee93"},{"sha":"c9eba94acafbbfed9f49f0cda2d6682463142196","author":{"name":"Aaron S. Hawley","email":"33bea6435d7defc0d2f5803f647c8432a437ec2e@gmail.com"},"message":"Comment out java.nio.charset.StandardCharsets to avoid Java 6 compiler error","distinct":true,"url":"https://api.github.com/repos/ashawley/scala-xml/commits/c9eba94acafbbfed9f49f0cda2d6682463142196"},{"sha":"56d2408880bbece1106ef67aa7b5be23018296fe","author":{"name":"Aaron S. Hawley","email":"33bea6435d7defc0d2f5803f647c8432a437ec2e@gmail.com"},"message":"Increase memory to 3.75G to avoid OOM","distinct":true,"url":"https://api.github.com/repos/ashawley/scala-xml/commits/56d2408880bbece1106ef67aa7b5be23018296fe"},{"sha":"94ebb62fa8674d9e1b8cfab05031df041f7e8ab5","author":{"name":"Aaron S. Hawley","email":"33bea6435d7defc0d2f5803f647c8432a437ec2e@gmail.com"},"message":"Remove debug line in XMLLoaderSpec","distinct":true,"url":"https://api.github.com/repos/ashawley/scala-xml/commits/94ebb62fa8674d9e1b8cfab05031df041f7e8ab5"},{"sha":"ab70b7a73e2e6ce9f5582769d110ee042223c19d","author":{"name":"Aaron S. Hawley","email":"33bea6435d7defc0d2f5803f647c8432a437ec2e@gmail.com"},"message":"Conform the names of generators","distinct":true,"url":"https://api.github.com/repos/ashawley/scala-xml/commits/ab70b7a73e2e6ce9f5582769d110ee042223c19d"},{"sha":"6c1315311d2f557ee4f3357d7f38d97c751ce4e3","author":{"name":"Aaron S. Hawley","email":"33bea6435d7defc0d2f5803f647c8432a437ec2e@gmail.com"},"message":"Add property test for XMLLoader.load(_: InputSource)","distinct":true,"url":"https://api.github.com/repos/ashawley/scala-xml/commits/6c1315311d2f557ee4f3357d7f38d97c751ce4e3"}]}
{"actor":{"display_login":"ashawley"}}