Why standardized Test Tool Interfaces? PDF Print E-mail

As a Software Test Engineer, You want to spend 100% of your time on test analysis and execution. Unfortunately, lot's of time is wasted on administrative issues, like

  • gathering requirements
  • mapping test cases to requirements
  • describing the test cases (it's in your head, but must be on paper)
  • reporting results
  • giving advice as to what parts can be tested at the next stage
  • chasing faults
  • re-testing test cases that already ran dozens of times (and still don't pass).
  • etc. etc.

Tools can help you with these tasks, but the common problem for open-source tools seems to be that they either supply in a small need or include too much functionality in order to attract the right attention. The commercial tools on the other hand are expensive, especially for smaller companies, but still do not co-operate well with some of the brilliant open-source tools.

The problem of tools not working together can be tackled by defining the interfaces between groups of tools. An important side effect is that the tool-makers can focus on their specific goal and let the functionality on the other side of the interface be covered by other tools. The extra benefit for the tester is that the best combination of tools can be chosen. And because these tools are focussed on their task, they have a better quality.