Re: Dogtail UI Harness Status
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
Re: Dogtail UI Harness Status
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
Dogtail UI Harness Status
Hi Josh, 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. Good news first. = 1 - Misc Fix Issues appear while developing the test cases. 2 - a new proposed method to test the reporting, following those steps: a. Open a presaved project b. create a report. c. export the report to HTML file. d. compare this HTML with a presaved HTML ref file after doing some filtering to remove the data modified every testcase like date. 3 - Test cases for adding new customer and vendor using a data driven testcases, the same way could systematically applied to other items in the Business menu. 4 - Test finding new customer and vendor using a data driven testcases, the same way could systematically applied to find other items in the Business menu. 5 - some test cases to test relatively complex and long scenarios from tutorial like Accounts Recievable and Accounts Payable 6 - More and cleaner comments for the test cases code. The bad news. = 1 - no testcases for preferences dialogs yet only check if the dialog appears properly. 2 - Some limitation on creating the account only Parent-child(2-Levels), can not go deeper than this. 3 - register processed using raw input and keyboard hot keys, dogtail has a limitaion in accessing current register. 4 - In Add new account wizard, selecting multiple categorize does not works properly. 5 - running the whole test suite may takes from 1-1:30 hours. according to my last run. Some statistics: Currently we have a wrapper for ~ 40 dialogs and widget. Number of testcases ~ 50. Total number of LOC ~ 3000. Fussy? Opinionated? Impossible to please? Perfect. Join Yahoo!'s user panel and lay it on us. http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7 ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
