Re: Gnucash UI dogtail test harness some ideas

2007-06-11 Thread Josh Sled
ahmad sayed <[EMAIL PROTECTED]> writes: >>> In the complex case of some XML file that was describing the tests more >>> fully >>> (or even "formally"), that file could contain a whole mini-language for >>> doing >>> test Setup ... > > I always prefer to use XML at its descriptive level, xml o de

Re: Gnucash UI dogtail test harness some ideas

2007-06-08 Thread ahmad sayed
Hi josh, >> I'm not sure that this XML file is useful. The idea is not in making the testplan in xml only, xml is only a suggested approach, the main idea is to separate the testplan from the code >> In the complex case of some XML file that was describing the tests more fully >> (or even "for

Re: Gnucash UI dogtail test harness some ideas

2007-06-06 Thread Josh Sled
ahmad sayed <[EMAIL PROTECTED]> writes: > 1 - Testplan editor is a common practice in Testing tools, in which user [...] > My suggestion here is to use xml with the following format > > Test the new Account dialog > I'm not sure that this XML file is useful. In the complex

Gnucash UI dogtail test harness some ideas

2007-06-05 Thread ahmad sayed
Hi all, I intend to do some modules around dogtail first, 1 - Testplan editor is a common practice in Testing tools, in which user could state the testcase formally, also could be used by the reporting tool to generate meaningful report, this formal description will be linked to a python met