I've been looking into software testing since we want to test and compare several tools (tools = software programs) made for the same goal, eg. all html editors. Although the tools we have now are open source, we are not interested in the code.

So that made me look at black-box/functional testing, but that's described as using the programs specification to create your test cases. What we wanted to do though is to use a more general test case for all the tools. That test case would fit the general specification of the domain these tools are build for, but not explicitly for any one of them.

Would that still be called black-box/functional testing or is there a different approach used for this?

And are there other recommendations for this type of 'test and compare' situation?

EDIT: after further reading, I think what I am looking for are System or Acceptance Testing techniques. But still, any other recommendation or correction is welcome.

  • What is the purpose of this ? Are you trying to decide which one your team/org should use ? Mar 17, 2013 at 14:06
  • I have to agree with Phil here. Could you elaborate on the business problem you're trying to solve? That will help tremendously in determining how to approach the problem.
    – corsiKa
    Mar 18, 2013 at 18:33

1 Answer 1


As with most other tests, let your Requirements drive your testing, without being tool-specific.

Do you have Requirements for what your tool-under-test must do? If so use that. Don't let the specifics of how the tool fulfills the Requirement become part of your test cases.

For example, if your tool must be able to open an existing HTML file, then don't include the keystrokes used within your test case. Just refer to the fact that you Open the file.

Your Answer

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

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