Test Analysis

Test analysis reads the test basis to identify testable features and define associated test conditions. It determines “what to test” in terms of measurable coverage criteria.

Main activities:

  1. Analyzing the test basis :
    1. Requirement specifications:
      1. Business requirements,
      2. Functional requirements,
      3. System requirements,
      4. User stories,
      5. Epics,
      6. Use cases,
      7. Similar work products that specify desired functional and non-functional component or system behavior
    2. Design and implementation information:
      1. System or software architecture
      2. Diagrams or documents
      3. Design specifications
      4. Call flows
      5. Modelling diagrams (e.g., UML or entity-relationship diagrams)
      6. Interface specifications
      7. Similar work products that specify component or system structure
    3. The implementation of the component or system itself, including code, database metadata and queries, and interfaces
    4. Risk analysis reports, which may consider functional, non-functional, and structural aspects of the component or system
  2. Evaluating the test basis and test items to identify defects of various types, such as:
    1. Ambiguities
    2. Omissions
    3. Inconsistencies
    4. Inaccuracies
    5. Contradictions
    6. Superfluous statements
  3. Identifying features and sets of features to be tested
  4. Defining and prioritizing test conditions for each feature based on analysis of the test basis, and considering functional, non-functional, and structural characteristics, other business and technical factors, and levels of risks
  5. Capturing bi-directional traceability between each element of the test basis and the associated test conditions
  6. The application of black-box, white-box, and experience-based test techniques can be useful in the process of test analysis to reduce the likelihood of omitting important test conditions and to define more precise and accurate test conditions.
  7. Acceptance test driven development (ATDD), which involve generating test conditions and test cases from user stories and acceptance criteria prior to coding, also verify, validate, and detect defects in the user stories and acceptance criteria.
Aix Observer
Aix Observer
Articles: 31

Leave a Reply

Your email address will not be published. Required fields are marked *