ISTQB_TEST MANAGEMENT_1.4 The Project Test Strategy _1.4.3 Definition of Test Objectives

 

Aspect	Details	Example/Notes
Test Plan Levels	Release level, project/master test plan, level test plan (per test level), special quality characteristic plans (e.g., security, performance)	Agile/hybrid projects: iteration test plan
Test Scope	Functional and non-functional features to be tested and delivered	Agreed upon by stakeholders
Project Test Objectives	Defined goals associated with features delivered for testing	Use S.M.A.R.T methodology
S.M.A.R.T Criteria	Specific: Clear and unambiguousMeasurable: Quantifiable progress criteriaAchievable: Feasible with resources and timeframeRelevant: Aligned to project objectivesTimely: Defined deadline	Ensures objectives are practical and trackable
Examples of Test Objectives	- Meet exit criteria within timeframe- Achieve quality KPIs (e.g., reduce customer claims)- Compliance with industry regulations- Secure data access- Functional and non-functional checks- Increase test automation level- Code refactoring without new defects- Validate interface security (e.g., XML validation)- Usability goals (e.g., task completion time)	Reflect all relevant quality and quantity goals
Quality Assessment	Should include domain experts’ evaluation and stakeholder feedback	Complements measurable objectives
Test Environments	Multiple environments may be needed; availability may be staggered	Impacts achievability of objectives and exit criteria
Additional Context Factors	See Section 1.2 (Context of Testing) for factors affecting objectives and scope	Consider organizational, project, technical, and environmental constraints

Definition of Test Objectives

│

├─ Test Plan Levels

│   ├─ Release Level

│   ├─ Project/Master Test Plan

│   ├─ Level Test Plans

│   └─ Special Quality Plans (Security, Performance)

│

├─ Test Scope

│   └─ Functional & Non-Functional Features

│

├─ Project Test Objectives (S.M.A.R.T)

│   ├─ Specific

│   ├─ Measurable

│   ├─ Achievable

│   ├─ Relevant

│   └─ Timely

│

├─ Examples

│   ├─ Exit Criteria

│   ├─ Quality KPIs

│   ├─ Compliance

│   ├─ Security & Access

│   ├─ Functional Correctness

│   ├─ Test Automation

│   ├─ Code Refactoring

│   ├─ Interface Security

│   └─ Usability

│

├─ Quality Assessment

│   └─ Domain Experts & Stakeholders

│

├─ Test Environments

│   └─ Availability & Resources

│

└─ Additional Context Factors

    └─ Refer to Section 1.2 (Context of Testing)

Q1: A test manager sets a test objective to "Increase regression test automation by 20% within the next release cycle." Which S.M.A.R.T criteria does this objective satisfy?

A) Specific, Measurable, Achievable
B) Relevant, Timely, Ambiguous
C) Specific, Timely, Irrelevant
D) Measurable, Ambiguous, Achievable

Answer: A) Specific, Measurable, Achievable

---

Q2: Which of the following is NOT an example of a project test objective?

A) Validating XML schema for interface security
B) Increasing team morale by organizing monthly social events
C) Meeting quality goals by reducing customer claims
D) Ensuring data access is available only to authorized users

Answer: B) Increasing team morale by organizing monthly social events

---

Q3: If multiple test environments are required but only one is available at a time, what impact does this have on test objectives?

A) Objectives may need to be adjusted for achievability
B) It will have no impact if deadlines remain the same
C) More environments should be built immediately
D) Objectives should be made more generic

Answer: A) Objectives may need to be adjusted for achievability

---

Q4: In an Agile project, what kind of test plan is typically agreed upon for each sprint or iteration?

A) Master Test Plan
B) Iteration Test Plan
C) Release Test Plan
D) Level Test Plan

Answer: B) Iteration Test Plan

Q5: Why is it important for test objectives to be relevant?

A) To ensure objectives are ambitious
B) To align testing efforts with overall project goals
C) To cover all test types
D) To meet regulatory requirements

Answer: B) To align testing efforts with overall project goals

1. What does the “A” in S.M.A.R.T test objectives stand for?
   a) Ambitious
   b) Achievable
   c) Accurate
   d) Applicable

2. Which of the following test plans focuses on specific quality characteristics?
   a) Master Test Plan
   b) Security Test Plan
   c) Release Test Plan
   d) Iteration Test Plan

3. What should a test objective include to be measurable?
   a) Subjective evaluation criteria
   b) Quantifiable progress indicators
   c) Vague success statements
   d) General goals

4. In defining test objectives, why should multiple test environments be considered?
   a) To reduce test effort
   b) To ensure test objectives are feasible
   c) To avoid test automation
   d) To increase defect rates

5. Which of the following is a valid exit criterion related to test objectives?
   a) Code review completion
   b) Meeting specified test coverage percentage
   c) Defining user manuals
   d) Scheduling meetings

6. What does a project test plan define for each release or iteration?
   a) Organizational goals
   b) Functional and non-functional scope
   c) Budget allocations
   d) Team structure

7. Which method helps in defining clear and structured test objectives?
   a) Agile manifesto
   b) S.M.A.R.T goals
   c) Risk analysis
   d) Boundary value analysis

8. Which aspect is NOT typically part of a test objective?
   a) Timeframe
   b) Functional scope
   c) Test environment availability
   d) Code implementation details

9. What role do domain experts play in test objectives?
   a) Writing test scripts
   b) Assessing quality levels
   c) Designing software architecture
   d) Managing test tools

10. Why is defining test objectives important in test management?
    a) To ensure testing is random and unstructured
    b) To provide clear direction and measurable goals for testing
    c) To delay project delivery
    d) To reduce communication with stakeholders