Skip to content
IRC-CodingIRC-Coding
Test ProcessTest PlanningTest ExecutionTest EvaluationTest ProtocolControl Procedures

Testing Process: Planning, Execution & Documentation

Complete guide to testing processes: test selection, data generation, execution, results evaluation, and protocol documentation with control procedures.

S

schutzgeist

1 min read
Testing Process: Planning, Execution & Documentation

Test Process

This article is a conceptual guide to the test process – including exam questions and key terms.

In a Nutshell

Planning → Execution → Evaluation → Documentation – run tests systematically, assess results, and record findings.

Core Breakdown

1. Test Planning

  • Select test methods (Unit, Integration, E2E)
  • Define test criteria (acceptance criteria)
  • Prepare test environment
  • Generate or select test data
  • Assign responsibilities

2. Test Execution

  • Run tests according to plan
  • Log results
  • Document deviations
  • Adjust tests as needed

3. Test Evaluation

  • Compare expected vs. actual results
  • Analyze deviations
  • Classify defects
  • Assess risks

4. Test Documentation

  • Create test report
  • Document results
  • Record approval or acceptance
  • Capture lessons learned

Key Exam Topics

  • Test method selection (Unit, Integration, System)
  • Test criteria (measurable, verifiable)
  • Test data management (Fixtures, Factories)
  • Test environment (Staging, Container)
  • Expected vs. actual comparison
  • Test report (contents: test case, result, defect, approval)
  • Control procedures (Reviews, Audits)
  • Acceptance report

Core Components

  1. Test Planning
  2. Test Execution
  3. Test Evaluation
  4. Test Documentation
  5. Test Data Management
  6. Test Environment
  7. Test Criteria
  8. Control Procedures
  9. Acceptance Process
  10. Lessons Learned

Practical Example (Login Feature)

Planning:
- Methods: Unit + Integration + E2E
- Criteria: Login with valid/invalid data
- Environment: Staging with test database
- Data: 5 test users (valid, locked, non-existent)

Execution:
- Unit: test validateLogin()
- Integration: test login against database
- E2E: run browser-based login

Evaluation:
- Expected: successful login for valid users
- Actual: 4/5 successful, 1 defect (locked user not rejected)

Documentation:
- Test Report TP-001
- Result: passed with 1 open defect
- Approval: conditional (defect must be fixed)

Common Exam Questions (Quick Answers)

  1. What belongs in a test plan? Methods, criteria, environment, data, responsibilities.
  2. What is expected vs. actual comparison? Comparing the expected outcome with what actually happened.
  3. What goes in a test report? Test case, result, defects, approval, date, responsible parties.

Key References

  1. https://www.istqb.org
  2. https://junit.org/junit5/docs/current/user-guide/
  3. https://testing.googleblog.com
Back to Blog
Share:

Nächster Artikel in Software Quality

Weiterlesen
Behavior Driven Development: BDD for Teams

Related Posts