One more ticket closed: #17, which pointed out that there was, until 2 days ago, insufficient checking on the markups being passed to Handlers, and no tests on what checking there was (much less everything there should have been).
This has now been rectified, and one more barrier in the way of the Grammarian demo has been pushed aside.
On the topic of the demo itself, I've gone crazy enough to talk myself into creating a vizualizer in SVG. Making simple SVG is really, really easy, so I'm hopeful that given a month of noodling about I can create a basic-but-fun datastructure browser. Because let's face it, a demo whose only product is some debug text and a datastructure is not exactly what captivates the kids these days. We're not working on TRS-80s anymore :(
Saturday, July 26, 2008
Thursday, July 17, 2008
All tests passing (again)!
Finicky, finicky stuff, but everything is a go again, and the codebase as a whole is better for it.
Yay, correctness!
This weekend I plan to push coverage back to 100% on all "finished" modules before restarting work on the Include pragma.
Yay, correctness!
This weekend I plan to push coverage back to 100% on all "finished" modules before restarting work on the Include pragma.
Friday, July 4, 2008
Oops
No, all tests are not passing.
The Text handler had a spurious 'exit;' in it, which was choking off all the REAL tests, nearly all of which were failing.
Looks like its problems are also being caused by 'endnode' -- but that's a well understood problem at this point, and the interactions here are far, far simpler than in Handler.pm. I'm hoping to have it fixed by tomorrow night.
The Text handler had a spurious 'exit;' in it, which was choking off all the REAL tests, nearly all of which were failing.
Looks like its problems are also being caused by 'endnode' -- but that's a well understood problem at this point, and the interactions here are far, far simpler than in Handler.pm. I'm hoping to have it fixed by tomorrow night.
Tuesday, July 1, 2008
All Tests Passing
Finally, all the original tests for Carrot (as of April!) are passing again. New coverage reports have been generated, and will continue to be as work progresses.
There are a lot of new tests that need writing before work on the Pragma is begun again, and not just because some existing modules are below 100% coverage due to rewrites -- during this long process I noticed several ways in which the existing suite was flawed. Having test coverage is excellent, but it's still no guarantee that you're testing for everything that can go wrong (of course!).
There are a lot of new tests that need writing before work on the Pragma is begun again, and not just because some existing modules are below 100% coverage due to rewrites -- during this long process I noticed several ways in which the existing suite was flawed. Having test coverage is excellent, but it's still no guarantee that you're testing for everything that can go wrong (of course!).
Subscribe to:
Posts (Atom)