=== Text of private mail to me dated Aug 26 2003
Hi,
Was looking for something to test the DB APIs. Your tool
looks the most promising. But, for ease-of-use, it will need to
provide a GUI and if possible support some auto-generation of
test-cases.
Check out their auto-gen feature. Would like to get involved
if I have some time.. Lets see... Do let me know if you have
something planned.
regards,
Mohan.
----
This started me off on the GUI tool development. A preliminary version is planned for release in version 1.9 or 2.0. GUI development is not my strong suit, and I am sure it will show, so if anybody wants to take a look at the code I will be cvs-ing sometime next week and improve it, let me know.
Thanks
Sujit
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Here is a preliminary design.
--- Sujit Pal <pal_sujit@hotmail.com> wrote:
> If you send me the source for the class you wrote, I can incorporate it into
> the GUI I am writing. Alternatively, if you feel more comfortable writing
> the GUI (this is my first swing app, the last time I wrote client side GUI
> code was for some applets some 5 years ago), let me know and you could take
> over the whole thing and I can give you cvs access.
>
> I thought about your original request some more over the last couple of days
> and I tend to agree with your viewpoint more now. Let me put into words what
> my plan is, and you can correct me where you disagree with me.
>
> The GUI should be able to browse the file system to pick up SQLUnit test
> files, and to load them into its memory.
> Once loaded, the file could be transformed into a DOM tree and the file
> could be browsed similar to the way one browses a DOM tree, with popups to
> populate individual elements.
> The GUI should support addition of new test nodes, deletion of test nodes
> and cloning (or pasting) of new test nodes from existing test nodes.
> The GUI should provide a hook to "build" node using an existing stored
> procedure and an existing database connection (configured in the
> <connection> node). So when this function is called, it will make an actual
> call to the database and build a node which can then be edited.
> Once all edits are done, the GUI should be able to persist the DOM tree back
> to the filesystem, using one of Save or SaveAs functionality.
>
> BTW, all my GUI has now are menus. The scope has increased quite a bit since
> we spoke last, so I am estimating it will take a week or two of my time (I
> work about 2 hours a day on this). If you think you can finish it earlier,
> feel free to take it over. Let me know, though, so we dont both do it at the
> same time.
>
> Thanks
>
> - sujit
>
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
=== Text of private mail to me dated Aug 26 2003
Hi,
Was looking for something to test the DB APIs. Your tool
looks the most promising. But, for ease-of-use, it will need to
provide a GUI and if possible support some auto-generation of
test-cases.
Another project I saw was:
http://utplsql.sourceforge.net/Doc/utgen.html
Check out their auto-gen feature. Would like to get involved
if I have some time.. Lets see... Do let me know if you have
something planned.
regards,
Mohan.
----
This started me off on the GUI tool development. A preliminary version is planned for release in version 1.9 or 2.0. GUI development is not my strong suit, and I am sure it will show, so if anybody wants to take a look at the code I will be cvs-ing sometime next week and improve it, let me know.
Thanks
Sujit
Here is a preliminary design.
--- Sujit Pal <pal_sujit@hotmail.com> wrote:
> If you send me the source for the class you wrote, I can incorporate it into
> the GUI I am writing. Alternatively, if you feel more comfortable writing
> the GUI (this is my first swing app, the last time I wrote client side GUI
> code was for some applets some 5 years ago), let me know and you could take
> over the whole thing and I can give you cvs access.
>
> I thought about your original request some more over the last couple of days
> and I tend to agree with your viewpoint more now. Let me put into words what
> my plan is, and you can correct me where you disagree with me.
>
> The GUI should be able to browse the file system to pick up SQLUnit test
> files, and to load them into its memory.
> Once loaded, the file could be transformed into a DOM tree and the file
> could be browsed similar to the way one browses a DOM tree, with popups to
> populate individual elements.
> The GUI should support addition of new test nodes, deletion of test nodes
> and cloning (or pasting) of new test nodes from existing test nodes.
> The GUI should provide a hook to "build" node using an existing stored
> procedure and an existing database connection (configured in the
> <connection> node). So when this function is called, it will make an actual
> call to the database and build a node which can then be edited.
> Once all edits are done, the GUI should be able to persist the DOM tree back
> to the filesystem, using one of Save or SaveAs functionality.
>
> BTW, all my GUI has now are menus. The scope has increased quite a bit since
> we spoke last, so I am estimating it will take a week or two of my time (I
> work about 2 hours a day on this). If you think you can finish it earlier,
> feel free to take it over. Let me know, though, so we dont both do it at the
> same time.
>
> Thanks
>
> - sujit
>
Mohan also sent me a java class which I plan to incorporate in the test generation action handler.