Page 1 of 1

API availability

PostPosted: Wed Jan 25, 2006 2:39 pm
by ricotero
Hi,
I\'m evaluating test management tools. Since I need to directly add the results from scripts I need to know when the 1.7 version will be available, at least a beta version. Additionally, I will like to know in which manner the API will be implemented (SOAP, XML over HTTP, precompiled library -- for which language--, etc etc)

Best regards to all,

Martín

PostPosted: Sun Jan 29, 2006 12:53 pm
by havlatm
XML / HTTP is choosen one. Time frame of 1.7 is several months. There is no accurate plan. However API will be implemented in later phase of 1.7. (if you don\'t write it earlier :D ), because there are signicicant changes in db schema now.

PostPosted: Tue Mar 07, 2006 3:50 pm
by Jenne
Hi,
do you have any information right now
WHAT we will be able to do with the API ?

Thanks

Jenne

PostPosted: Tue Oct 03, 2006 11:20 pm
by jhenthorn
I am also very interested in the progress of the TestLink API.

Right now I have integrated testlink with my testing framework by manipulating the database. That means an instant headache when the schema changes (as it has since I've been doing this).

News of the XML-RPC API is very good. More Please!

PostPosted: Mon Oct 09, 2006 8:13 pm
by asielb
I wish I had more to report. Unfortunately I was originally expecting to be able to work on this and have had very little time to work on it. Therefore I have made some progress but have not finished. If someone is interested in trying to finish implementation of some of the functions or provide feedback I am fine with checking what I do have into cvs. If someone is interested in this please send me an e-mail through the testlink-dev mailing list.

I will post info on the mailing list and/or testlink.org when I have more info to provide.

PostPosted: Mon Oct 09, 2006 8:16 pm
by asielb
I also just noticed that this was a question for 1.7. I still need to begin porting what has been done to 1.7. So getting things working on 1.7 will be even more difficult unfortunately.