What Diagrams Should QA-engineers Be Familiar With?

What Diagrams Should QA-engineers Be Familiar With?
February 17 12:59 2017 Print This Article

The biggest problem of any software testing – you should test everything. And this “everything” is very hard to transform into a quantity form. But a tester should realize what is under test and what is not. This relates to a concept of test coverage.

The special diagrams are of great use in this case. Now it is time to remember what schematic representations are successfully applied during the test process.

testing-diagrams

6 Most Popular Diagrams in Software Practice:

  1. State transition diagram – a table which helps to understand what task should be executed, what modifications it is undergone, and the actual result of these changes.
  2. Mind map – this collaborative tool assists to understand the cause-and-effect relationship of the current issue by describing each phase of the process.
  3. Context diagram – it illustrates all external factors or entities which may interact or affect the system.
  4. Block diagram (flow chart) – may be applied to the test plans, requirements or test strategy and illustrates the process or monitor statistical analysis.
  5. Entity-relationship diagram (ER diagram) – shows the details of database storage via graphical elements: entity set (rectangle), their attributes (oval), and links (diamond).
  6. Wireframe – the screenshots or drawn by hand images which visualize the future product and help to test its design.

The aforesaid illustrative tools are of great use during any type of testing (exploratory testing, usability testing, user interface testing, unit testing, white-box testing, functional testing, ad-hoc testing, and so on). Thus, each tester should be familiar with such diagrams and be able to apply them if required.

Related Posts:

About Article Author

view more articles
Nataliia Vasylyna
Nataliia Vasylyna

View More Articles