Sobes.tech
Junior

What testing methods do you know?

sobes.tech AI

Answer from AI

  • Functional testing:
    • Unit testing: Testing the smallest isolated parts of code (functions, classes).
    • Integration testing: Checking the interaction between different modules or components of the system.
    • System testing: Testing the entire integrated system for compliance with requirements.
    • Acceptance testing: Testing by end-users or business representatives to confirm it meets their needs.
  • Non-functional testing:
    • Performance testing: Assessing system performance under load.
      • Load testing: Testing the system under expected load.
      • Stress testing: Testing the system beyond expected load to determine failure points.
      • Endurance (Soak) testing: Checking system stability during prolonged operation under load.
    • Security testing: Assessing system security against threats.
    • Usability testing: Checking how user-friendly the system is for end-users.
    • Compatibility testing: Testing system operation across different environments (browsers, OS, devices).
    • Reliability testing: Assessing the system's ability to operate without failures over a certain period.
    • Maintainability testing: Evaluating how easy it is to make changes to the system.
    • Portability testing: Assessing the system's ability to be transferred to another environment.
  • Change testing:
    • Regression testing: Re-testing previously tested functionality after changes to identify new defects.
    • Re-testing (Confirmation testing): Re-testing a specific defect after fixing it to confirm its resolution.
  • Structural testing (White-box testing): Testing internal structure and logic of code.
    • Statement coverage: Covering all code statements.
    • Branch coverage: Covering all branches of code logic (conditions).
    • Path coverage: Covering all possible execution paths of the code.
  • Black-box testing:
    • Boundary value analysis: Testing boundary input values.
    • Equivalence partitioning: Dividing input data into equivalent classes.
    • Decision table testing: Using decision tables to test combinations of conditions and actions.
    • State transition testing: Testing transitions between different system states.
    • Use case testing: Testing the system based on user scenarios.
  • Exploratory testing: Simultaneous test design, execution, and result analysis.
  • Risk-based testing: Prioritizing testing based on potential risks.
What testing methods do you know? — QA / QA Automation - sobes.tech