I would be willing to help test TestLink for bugs etc. I have submitted a few already. I was wondering if you have a suite of tests written up for testing the various parts of TestLink.
I know it's kind of ironic to use your own product to test your own product, but if there is a standardized list of tests, it would make it easier for people to help test things.
You can hand a tarball to anyone and tell them to help test it but, without guidelines or structure to the testing, you will get back lots of oddball non-reproducible things.
If you have anything set up, please let me know. I would be willing to help. Otherwise, I will continue my random testing
We are looking for somebody who is able make some automatized regression set of test. So It will be great job if you are experienced in some such tool.
Another point to make testing better is http://testlink.org/tl4tl/login.php. Feel free to look there. It's empty specification which wait for somebody who make it working.
Let me know if would like to do it. And I raise your rights there.
I created a login. It looks like there are no test cases created. In my spare time, I can add some tests. I'll need my rights bumped up.
I don't have good enough experience with automation software to get into that.
Are there any specifications for what TestLink SHOULD be doing? Something to use as a guideline? Any list of features that will be added for the final 1.7 or a list of items added since 1.6.2?
Any information you could give me would help me get it started. If there are things you don't want posted on here, feel free to send me a private message or e-mail.
I think we should select a web application automation test tool like this and start collecting (in a CVS directory) more and more test cases to test TL.
Having a Test case specification and a test plan, is a milestone step, at least IMHO before thinking about test automation.
I would like to use any of the automation test tools (another choice can be Watir, or Selenium, or Badboy), an we appreciate any help to build some automated tests.
Write now we have no time to use in this task.
Do you want to try to help use with jamaleon ?
I will be more than happy to help building up an automated test suite for TL. I am in the process of choosing such kind of tool for my job. I am not an expert of Jameleon but I did like the idea of having a general test engine that (using plugins) is able to test Web Applications but also desktop applications and more.
I will give a look to the tools you are suggesting too.
I think the steps we should move on are the following:
1) Choose the test automation tool
2) Think a way we will use to integrate the tool with TL so that Test Cases could be written in TL and used in the automation test tool.
3) Converting (when possible) the manual TL test cases into automation test scripts
I understand that there is no time allocated on this task but may be steps 1) and 2) can be done without coding and only discussing on the forum.
OK if you want to do it, and without any type of offense is not a surprise for me that you or any other people, will be more happy or willing to do coding of the automated test cases (because is like any other type of coding), instead of firts thinking and writing the test suite.
Is the old issue about:
coding is cool, writing specs no.
Anyway, at this time IMHO the first issue for the development team is to test as much as possible (with user community help) in order to release a good or as good as possible TL 1.7.
Let us know your experience with jamaleon.
I've used Quick Test (a commercial product) and really is very, very good.
I also will be happy to have automation to do regression tests.
Regarding the issue "writing the tests in test link and using it on ...".
I have limited experience with Test Director, but there you:
1. write the test steps in "human language"
2. record the tests using Quick Test
3. save the test scripts on Test Director or link from Test Director to Quick Test.
I don't want to loose the focus:
Test Link IS NOT AN AUTOMATION TEST TOOL, is a TEST & REQUIREMENT MANAGEMENT tool, that has to have (in the future) the possibility to interact with one of the existent automation test tools.
I understand and agree perfectly with you.
Let's start writing the test suites.
If you note I was writing about "Converting (when possible) the manual TL test cases into automation test scripts" that means of course that a manual test should already be there.
Where should we start from in the Test Suite writing?
