Hi Josh,
I wrote my first documentation document on the gnucash dogtail UI test harness,
it does not contains your request yet, but it just a start if it is ok, i'm
going to follow it with other document, I attached it in open document format
(ODT), I hope if this format is suitable or you coul
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:
>>
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 thos
Sorry Josh I might be not clear in my previous Email, the specific repository I
mentioned in my Email, is the repository provided by Google itself.
not sure if all could access the following links but I think mentor and student
at least could access it
the repository will be here
http://google-
Hi Josh,
There is request from google to upload our soc code to a specific code
repository, so I confirm that all my files indicate that it is under Gnu
General Public License, sorry not sure how important this issue is, but i think
other gnucash SOC projects should consider this issue also.
B
Derek Sorry again for the delay , this time i didn't see the Email :( , i saw
it while doing my routine orginization to my mails
The issue of using coordinate or hotkeys is only with widgets that have some
problem currently The register and the treetable in account page, other
invisible widget
Sorry for the delay, I was out of home for 3 days:).
>> (As Derek asked:) are these window x,y coordinates, or logical widget
>> locations?
>> Based on the command above I'd ASSUME it's logical widget locations..
?? But I'm wondering how it deals with invisible widgets.
yes it is logical,
yes i
Hi Josh,
After sending this Email, i tried to commit some codes, and i got and error i
notice that, i didn't do svn add to the test-dogtail, but I thing it works fine
now.
Boardwalk for $500? In 2
Hi Josh,
Waiting your comments :), I committed the code to the dogtail branch i created
a new dir under src called src/test-dogtail it contains my up to date code.
Best regards,
Ahmed Sayed
- Original Message
From: ahmad sayed <[EMAIL PROTECTED]>
To: Josh Sled <[EMAIL PROTE
Derek,
Sorry, I found that gnucash devel is very busy those days so I expect that it
will be better to send this issue in private Email.
Best regards,
Ahmed Sayed
Expecting? Get great news right away with
Hi Josh,
Sorry for my long silence i got some issues with my PC lately, I solved it at
last,
currently i have a mix of good news and bad news.
the good news is:
1 - Currently we have wrapper to most of dialogs, our wrapper module reach more
than 1000 LOC.
2 - I'm able to test the register and
when writing a test case we always has setup and teardown, the both these
methods will be different according to the testcase, some testcase will need to
have a gnucash without any data file, others will require this data file, these
operation will be done in the setup,
in general
the basic t
andi5 said
>> I just remembered that there is the environment variable GNC_GCONF_PATH
>> to replace the prefix /apps/gnucash. I have no clue whether this is
>> helpful here at all.
look like a safer solution, i'm not sure if (gconftool-2 --recursive-unset
/apps/gnucash) will cause any harm.
Hi Josh,
>> The second item implies that the test framework should be able to modify
>> gconf keys before starting gnucash (in this case, to remove the "have seen
>> the first-time dialog" key). Which makes perfect sense, but I don't recall
>> that this has been called out before.
Yes, i impleme
Hi all,
This is Just a base for the gnucash testplan it will be developed over time,
things may be removed and added. but it just beginning, The test cases not
going to follow this order in creation, also there still TBD (to be done)
issues, it is open for suggestions.
Best regards,
Ahmed Say
Thank you, David
>> I thought dogtail could uniquely identify widgets by their name
The problem is with the widget that does not have name or dialog that have no
title, also window that does not have no title, so to avoid adding user visual
change, you agree with me that adding description wil
Hi josh
1 - There is a dialogs with no title like process payment, which i need to make
dogtail detect the existance of the dialog, so This issue could be solved by 2
ways,
a - Add Title to this dialog.
b - add an accessible description for this widget.
Both may require
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
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
Thank you Derek,
>> Oops, I left you off this. I'm very sorry.
No problem I already in the gnucash-devel mailing list :), of course if you
mean me ;) .
BTW: after subscribing I waited to get the confirmation Email, but not getting
it, by chance while looking at my spam folder I found it marked
20 matches
Mail list logo
