Software Quality Assurance & Testing Stack Exchange is a question and answer site for software quality control experts, automation engineers, and software testers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am working on an agile team building a web-based product.

We do have jUnit tests and API automation as well. However since we iterate fast, more and more test-cases are being added or updated everyday.

My problem is that there is no central list of test-cases. Is there any tool which I can use to maintain list of tests and individual test details?

share|improve this question
Why do you need a central list of tests? The tests are included with the code, not? And thus always up-to-date. Just make sure they do not break, run them daily on a continuous integration server. :) – Niels van Reijmersdal Jul 11 '14 at 8:09
I want to disable some tests based on the functionality in some builds. So I can get the list of tests and generate some list based on that , I can run only those tests. Not everything everytime. – Jijoy Jul 11 '14 at 11:17

Test documentation:

It should be possible to generate code documentation with something like Doxygen or an alternative. (Assuming all the automated test-cases are started with a (unit) test-runner which uses a sort of class system in code.) Run the doc-generator only on the directories containing the tests. This should result in a list of all methods in the classes. Each method is a test, this could be the list you are looking for. Often these tools generate a method list and details click-through in the form of HTML pages.

Grouping tests:

Understanding you want to run the test-suite partial. I think its better to group your test-cases and let the runner only start the groups you want to run.

Here are some links that describe grouping for popular test-runners:

Start grouping the old tests and make sure everyone who creates a new tests to put it in one or more groups. Motivate them by telling them it will make local tests runs faster.

share|improve this answer

Basically you want to avoid building custom application for tracking dependencies?

One way would be to have a wiki, one page per test. Wiki pages will have tags based on functionality. To run a test, you first run a search query on wiki, get pages matching criteria, convert page names to test names, and run them. And pages also can hold any other relevant info about tests. With version control.

This kind of flexibility is why FOS wiki (which we use) is going strong even if soon will be 20 years old.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.