Test planning/documentation/management tools

Question

I\'m looking for a good, preferably free, test planning and documentation tool. Ideally something that will keep track of which tests have been run against which software versio

Answer 1

I've heard good things about Fitnesse but I don't know how good it's test tracking is.

I know I just recently saw a slick looking test tracker for Trac or something, but I can't find it now...

Answer 2

Yes, we do run tests, but not nearly as many as I'd like !

I highly recommend TestLink - the list of tools that you linked to shows that it's had more downloads than all of the other tools put together.

Answer 3

We use a home-grown Access database.

This database keeps track of our requirements, test cases, test plan and test runs. We're able to produce an up-to-date RVTM, keep track of progress against the plan, and assign tasks to testers. We integrated it with Outlook, so each tester is assigned a task from the plan by the QA lead. When they're complete, they just tick it off in Outlook and it updates the database.

For our small team of testers it works nicely, and we're free to customize it however we want.

Answer 4

I've used QualityCenter/TestDirectory for a long time.

I'm now using testlink and I must say that I prefer QualityCenter/TestDirectory by far, even if it based on some buggy ActiveX control.

QualityCenter/TestDirectory is more easier to use and the interface is quite better.

TestLink and QualityCenter/TestDirectory are mainly for manual test case (however, you can use Quick Test Pro on QualityCenter/TestDirectory to automatize your tests).

Fitnesse is another kind of tool in my mind : basically, you write your test case on a wiki and link that to a JUnit test. Another tools like that are GreenPepper, Concordion, etc.

Answer 5

We use Quality Center / Test Director stuff. Its expensive as far as I know, and it's not that great.

Answer 6

One thought, and perhaps not a good one, would be to have every test submit a ticket to your ticketing system when it's run indicating the test name, build version, and date, and test results.

That would make the results searchable later-on.