My own tests come from 3 sources. First, I almost always do test-driven programming, and these tests become the first part of the test suite. Second, any bug, I add a regression test. Third, I sometimes explicitly want something in the test suite that's not there from the other two sources, and add that as the last, pre-release phase. More often, I have cast the net wide in the development tests and bug-fix tests, so that when the last bug is fixed I have a quite adequate test suite already.
Also, I often prioritize debugging and tracing tests, sometimes writing the logic before the code that they debug and/or trace. That way they are available when I develop. Of course, I'm always eager to do the "real" programming. But if it's trace/debug stuff you *know* you'll need (and often you do), you gain time overall by delaying work on the core logic until they are in place. This relates to testing, because it means when I finish development my trace/debug code is itself thoroughly tested. I often have tests of the trace and debug logic in the test suite. This is not too hard to do if you've developed the trace/debug logic and debugged it along with the main code -- you develop it on a test-driven basis and when done, simply add that test to the test suite. I notice that other programmers rarely test their diagnostics and tracing code, and it can be a chore, but I find it's a life-saver. On Wed, Aug 10, 2016 at 12:19 PM, <[email protected]> wrote: > Thanks! > > I read the FAQ, but dismissed the on-the-fly grammar fiddling as an > advanced topic that I didn't need. Now I find it's one of the basic > concepts I want to use. :-) > > I've read most of those tutorials. In particular, Stuifzand's tutorial > includes the tantalizing statement, "[a]nd this leads to developing a set > of test files...." What I'm trying to ask is *how* to develop these > tests. Re-reading the tutorials, I still don't see any help in this > direction. (Of course, I missed FAQ 126, too.) > > Thanks for your patience! > > - Ryan > > On Tuesday, August 9, 2016 at 10:04:09 PM UTC-6, Ron Savage wrote: > >> (1) On-the-fly fiddling of the grammar is in - ta-da! - the FAQ: >> http://savage.net.au/Perl-modules/html/marpa.faq/faq.html#q126 >> >> (2) Tutorials and articles are on Marpa's unofficial home page: >> http://savage.net.au/Marpa.html#Tutorials >> <http://www.google.com/url?q=http%3A%2F%2Fsavage.net.au%2FMarpa.html%23Tutorials&sa=D&sntz=1&usg=AFQjCNHHqm7mWUJbe8CaSmwlFODdtPUwYA> >> >> -- > You received this message because you are subscribed to the Google Groups > "marpa parser" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "marpa parser" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
