API Beta

[Laurent]

Hi,

I am a big fan of testlink and have used it in several companies already (It reminds me a lot of a tool developed by Ericsson called TCL (for test case library)). So first of all, congrats to the development team, you got it right, in many cases much more than commercial solutions

We are running test cases written in Lua on embedded devices. There is an xml RPC module written for Lua and I have converted your python client sample to Lua (which I wouldn't mind providing if you want).

I would like to test the API, however, I have attempted to connect to you demo installation without success. What is the best way for me to proceed. Any build I could upgrade to (we are currently 1.7.0 and see that 1.7.3)? I read somewhere that the RPC server could be an "add-on" to 1.7.x?

Any information would be very useful. This is the last step to close our continuous integration process.

Again, great job, this is excellent.

/Laurent
P.S.: Do you take donations? Being a startup we are not "quite rich" but willing to contribute to keep this project running.

[fman]

1. get code from CVS head, there is API code inside.
2. We will say something about your donation offer, I will talk with other project leaders.
You can contact me to francisco.mancardi@gmail.com

3. Please add your company to forum

[fman]

You can also help us writting user level documentation, case studies, tips notes, or whaterver you think can be useful to help users to use TL with a minimal pain.

[Laurent]

I took a look at your user's guide for 1.7.

While it contains some great info, I do think that it is too "dev." oriented by it usage of UML like diagrams for instance. Any areas where you think that there would be a need for improvments?

Also, I really think that setting up a TL install which contains the test spec. for testlink itself would be great (all users would be guest) - yo umay have that already. Then you can see what a real test specification is, how it integrates with Mantis, how do you create regression tests from bugs entered by users, transfer feature request into "product requirements", etc. The demo server is great for playing around, but is also full of garbage.

Do you write any kind of unit tests? I am not a PHP guy (I work in embedded) but a friend of mine told me that there are excellent PHP unit framework out there. Ever consider doing continuous integration with test link?

We gather a bunch of testers willing to contribute a little bit (hey, they get this great tool for free).

If you think that this can fly, I'll try to gather some people. After all the Mozilla foundation works like this ... Ever thought of contacting them?

Ciao!

[havlatm]

Hi we interested in cooperation with your guys.
Mozilla foundation uses different tool: lintus. I asked one guy from QA team. And they seems to be satisfied by own tools.

[Laurent]

after talking to fman, I went to their web site but haven't seen any information as far as joining the team or anything (I will send an e-mail to the admin).

I couldn't log to their TL server as well - What is the story on this? Who should I contact?
I also think that with the API, a lot of automation can be achieve leaving the manual testing for UI validation/verification.