Re: Dogtail UI Harness Status

[ahmad sayed]

Hi Josh,

Thank you very much for your positive feedback,honestly I have a stomach lately 
like the one I used to have before receiving my exams results:), that what keep 
me silent.

Josh Said:
>> If I wanted to add a test for the Scheduled Transaction subsystem ... let's
>> say consisting of:
>> 1/ creating a new Scheduled Transaction with given parameters.
>> 2/ running the Since Last Run dialog.
>> 3/ inspecting a value in the tree view/model.
>> 4/ manipulating the tree view; closing the dialog.
>> 5/ re-opening the Since Last Run dialog.
>> 6/ inspecting a value in the tree view/model.

>> I guess I'm looking for a bit of high-level documentation.  I'm sure I can

>> figure it out if I spend enough time with the code, but something short that

>> points me in the right direction would be great.


I'm going to write a tutorial to be uploaded to common place (e.g. to gnucash 
wiki),  your suggested testcase will be my start point, i'll start it tomorrow 
as it is now 2 AM in my country :).

I plan to finish documenting all the testsuite related technical details before 
the school start,

also i would like to keep working on the testsuite there is still a lot of work 
todo,
1 - adding more testcases, 
2 - figure out how to speed it up
3 - link the testsuite to the makefile.
4 - add more dialogs and custom widget wrappers.
5 - Solving issues with with the register, and account Trees.
6 - more Testing to the testsuite ፡).





   

Moody friends. Drama queens. Your life? Nope! - their life, your story. Play 
Sims Stories at Yahoo! Games.
http://sims.yahoo.com/  
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: Dogtail UI Harness Status

[Josh Sled]

ahmad sayed <[EMAIL PROTECTED]> writes:
> In this phase of SOC the following updates done to the Dogtail UI Harness 
> project, the status as usual is mix of bad and  good news.

Ahmad...

Congrats on a modestly successful Summer of Code project.  I'm sure that
there's good and bad parts, but that's always the case. :) However, it looks
like we have both a framework for running dogtail-based tests, and a whole
suite of code for interacting with GnuCash and exercising parts of the
user interface.  :)


If I wanted to add a test for the Scheduled Transaction subsystem ... let's
say consisting of:

1/ creating a new Scheduled Transaction with given parameters.
2/ running the Since Last Run dialog.
3/ inspecting a value in the tree view/model.
4/ manipulating the tree view; closing the dialog.
5/ re-opening the Since Last Run dialog.
6/ inspecting a value in the tree view/model.

... how would I go about it?  What would I want to add or extend, and in what
files.  How to invoke just that test to try it out?

I guess I'm looking for a bit of high-level documentation.  I'm sure I can
figure it out if I spend enough time with the code, but something short that
points me in the right direction would be great.

-- 
...jsled
http://asynchronous.org/ - a=jsled; b=asynchronous.org; echo [EMAIL PROTECTED]


pgpGAvmQYJPzH.pgp
Description: PGP signature
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel