Please enable JavaScript.

Coggle requires JavaScript to display documents.

ISTQB Study - Coggle Diagram

- - - - Entry & Exit Criteria
      - Test Plan: contains info about the test basis
      - Test monitoring metrics
  - - - Progress Reports
      - Test Summary
      - Control Actions List
      - Task Completion
      - Resource allocation
- - - - Load
      - Stress
      - Endurance
      - Spike
    - - i. Variables that are never used.
      - ii. Security vulnerabilities.
      - iii. Programming Standard Violations
      - iv. Uncalled functions and procedures
  - - - Uses tester's experience to identify tests not easily captured by formal techniques
- - - -  Reducing risk
      -  Verifying whether the functional and non-functional behaviors of the component are as designed
      - and specified
      -  Building confidence in the component’s quality
      -  Finding defects in the component
      -  Preventing defects from escaping to higher test levels
    - -  Detailed design
      -  Code
      -  Data model
      -  Component specifications
    - -  Components, units or modules
      -  Code and data structures
      -  Classes
      -  Database modules
  - - -  System and software requirement specifications (functional and non-functional)
      -  Risk analysis reports
      -  Use cases
      -  Epics and user stories
      -  Models of system behavior
      -  State diagrams
      -  System and user manuals
    - -  Applications
      -  Hardware/software systems
      -  Operating systems
      -  System under test (SUT)
      -  System configuration and configuration data
  - - - Top-Down
      - Bottom-Up
      - Big Bang
    - -  Software and system design
      -  Sequence diagrams
      -  Interface and communication protocol specifications
      -  Use cases
      -  Architecture at component or system level
      -  Workflows
      -  External interface definitions
    - -  Subsystems
      -  Databases
      -  Infrastructure
      -  Interfaces
      -  APIs
      -  Microservices
  - - -  User acceptance testing
      -  Operational acceptance testing
      -  Contractual and regulatory acceptance testing
      -  Alpha and beta testing.
    - -  Business processes
      -  User or business requirements
      -  Regulations, legal contracts and standards
      -  Use cases and/or user stories
      -  System requirements
      -  System or user documentation
      -  Installation procedures
      -  Risk analysis reports
    - -  System under test
      -  System configuration and configuration data
      -  Business processes for a fully integrated system
      -  Recovery systems and hot sites (for business continuity and disaster recovery testing)
      -  Operational and maintenance processes
      -  Forms
      -  Reports
      -  Existing and converted production data
- - - - Tracking of anomalous test results