Right now my company uses a large excel spreadsheet to create 'tests' for surveys we develop. Each column is one test through the survey. Each field is the answer you should choose. While this system does work and is quite thorough 99% of the time. It is very time consuming. I'm curious about what other types of systems or documentation other people use when creating test cases.

  • 1
    Can you be more specific about why it is very time consuming to use a spreadsheet?
    – user246
    Mar 4, 2016 at 15:01
  • Not really. It just takes a lot of time and I'm wondering if anyone would want to share how they build test cases.
    – Nibb
    Mar 4, 2016 at 16:03
  • 3
    It is a fact of life that documenting your manual tests and tracking their execution takes longer than just running the manual tests. Have you tried doing a Google search for test case management systems? If so, what are you looking for that the Google search didn't cover? And is it possible to automate any of those tests? Please include your answers in your original question.
    – user246
    Mar 4, 2016 at 16:19
  • Test Case Management Tool : testlink can be used. It is simply not user friendly. It is a free and open source and can be easily configured.
    – Bhakti
    Mar 31, 2016 at 7:47

1 Answer 1


There are two very distinct aspects to this: Automated Testing and Test Case Management.
Some organizations that invest heavily in Automated Testing find that they don't actually need a Test Case Management tool because all their testing can be seen by looking at the automated test cases and their structure and organization.

Test Case Management

This is where the list of test cases and associated documentation is stored. This usually refers to test case management systems such as TestLink, TestNG, IBM Rational Quality Manager, HP Quality Center, QASymphony qTest etc.
In some organizations test writing activities themselves (tickets) will be managed through a system like Jira, Trello or Pivotal Tracker. Other organizations may simply prefer to use a bare-bones tool like Excel or even just plain text files to avoid the overhead of using a higher level system to manage test cases. The choice will depend on your situation.

Automated Testing

This is about actual automated testing using programmatic tests that you write, either backend or front-end UI tests. This often means using frameworks such as selenium, capybara, etc. and languages such as Ruby, Python, Java and C# Ultimately this is the best way to address the time-consuming issue. If you consider the number of cases X the number of devices and browsers, you quickly get to a non-sustainable point.
In addition to the backend programmatic solution, there are also a number of gui tools that can be suitable for non-programmers who are coming from an 'excel type' solution, such as the seleniumIDE (A firefox extension) or a cloud service like GhostInspector which lets you build tests in a web ui with point and click. You'll still need to learn about css and identifying elements and the like.

  • Thanks for the information. I appreciate the well thought out answer
    – Nibb
    Mar 5, 2016 at 14:45

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

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