Skip to content
IRC-Coding IRC-Coding
Testing Process Test Planning Test Execution Test Evaluation Test Protocol Control Procedures

Testing Process: Planning, Execution & Documentation

Master the testing process: test selection, data generation, execution, result analysis, and protocol creation with control procedures.

S

schutzgeist

2 min read
Testing Process: Planning, Execution & Documentation

Test Process

This article is a term explanation for the test process – including exam questions and tags.

In a Nutshell

Planning → Execution → Evaluation → Documentation – systematically conduct tests, assess results, and document them.

Compact Technical Description

1. Test Planning

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

2. Test Execution

  • Execute tests according to plan
  • Document results
  • Record deviations
  • Adjust tests as needed

3. Test Evaluation

  • Perform target-actual comparison
  • Analyze deviations
  • Classify defects
  • Assess risks

4. Test Documentation

  • Create test report
  • Document results
  • Document release/acceptance
  • Record lessons learned

Exam-Relevant Key Points

  • Test method selection (Unit, Integration, System)
  • Test criteria (measurable, verifiable)
  • Test data management (Fixtures, Factories)
  • Test environment (Staging, Container)
  • Target-actual comparison
  • Test report (Contents: test case, result, defect, release)
  • Control procedures (Reviews, Audits)
  • Acceptance protocol

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 Function)

Planning:
- Method: 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 DB
- E2E: perform browser login

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

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

Typical Exam Questions (with Brief Answer)

  1. What belongs in a test plan? Methods, criteria, environment, data, responsibilities.
  2. Target-actual comparison? Compare expected result with actual result.
  3. Contents of a test report? Test case, result, defects, release, date, responsible parties.

Most Important Sources

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