ISTQB_TEST MANAGEMENT_1.4 The Project Test Strategy _1.4.1: Choosing a Test Approach

1.4 The Project Test Strategy 


Aspect 
Explanation
Organizational Strategy Assumed to be defined; also called "organizational test practice" per ISO 29119
If Not Defined? Test Manager must consult stakeholders to define what's missing
Definition – Project Test Strategy Tailored approach to testing for a specific project, release, or system
Purpose Ensure business goals and quality expectations are met
Scope Can apply to a project, release, test level, or type
Documentation Usually part of a test plan, but may be in other documents too
Mandatory Documentation? Depends on development model, contracts, or regulations
[ Project Test Strategy - Intro ]
        |
  ---------------------------------------------------
 |                   |                      |                       |
Org Test Strategy   Missing Info        Project Strategy         Documentation
 |                   |                      |                       |
Assumed present     Clarify w/          For project/release       In test plan
(ISO 29119-3)       stakeholders        or specific level         or other docs
                                         Aligns with org goals     Context-dependent
                                                                  May be required by law
[ Choosing a Test Approach ]
        |
 ----------------------------------------------------------------------------------
 |                |                    |                  |                     |
Project Context   Test Levels       Test Types       Test Techniques     Influencing Factors
 |                |                    |                  |                     |
Objectives       Unit               Functional         Static (e.g. Review)  Org Strategy
Resources        System             Performance        Dynamic (e.g. Exec)  Test Team Skills
Responsibilities Acceptance         Security           Exploratory           Project Lifecycle
                 ...                Usability           Scripted, Manual     Regulations


Aspect Details
Purpose of Test Strategy Guide all test activities: objectives, resources, schedule, and responsibility
Tailoring to Project Must adapt to the specific needs and context of the project
Key Decisions in Test Approach - Test Levels (e.g., Unit, System, Acceptance)- Test Types (e.g., Functional, Performance, Security)- Test Techniques (e.g., Static, Dynamic, Exploratory)
Flexibility (Theory) Any test type can be executed at any level; any technique at any type
Reality (Practice) Effectiveness/efficiency depends on correct selection & combination
Examples - Code maintainability → static analysis - Performance → scripted tests - Usefulness → manual acceptance tests with users
Influencing Factors - Organizational test strategy - Project context - Regulations - Resources and skills
Importance Proper selection of levels/types/techniques directly impacts test effectiveness and efficiency

Q1 – K2 (Understanding Concepts)

Which of the following best describes why selecting the right combination of test levels, types, and techniques is important?

A. It ensures more test cases are written
B. It reduces the cost of test environments
C. It maximizes effectiveness and efficiency of testing
D. It guarantees 100% defect detection

Correct Answer: C
Explanation: The proper combination leads to better efficiency and outcomes.


Q2 – K3 (Application)

Scenario: A developer is concerned about code maintainability. Which of the following is the most appropriate testing approach?

A. Scripted UI tests
B. Load testing
C. Static code analysis
D. Manual system testing

Correct Answer: C
Explanation: Static analysis is efficient for evaluating code quality and maintainability.


Q3 – K3 (Application)

Scenario: You're managing a web app project with tight deadlines. It must support high performance and pass functional validation with real users.
Which combination is most effective?

A. Static analysis + Manual unit tests
B. Code review + Performance scripts + Acceptance tests
C. Load testing only
D. Manual tests by developers

Correct Answer: B
Explanation: This covers maintainability, performance, and user validation effectively.


Q4 – K4 (Analysis)

Scenario: In a large-scale Agile program, you have automated unit tests, but production bugs reveal performance issues. You also have business users willing to validate product features.
What should you recommend changing or adding?

A. More exploratory testing at unit level
B. Add scripted system-level performance tests and manual acceptance tests
C. Add only static testing
D. Remove unit tests and switch to exploratory system testing

Correct Answer: B
Explanation: You need performance testing (scripted) and usability validation (manual/user).


Q5 – K4 (Analysis)

Scenario: A new regulatory requirement mandates accessibility compliance. Your current test strategy includes only functional and performance tests.
How should the test approach be updated?

A. Remove performance testing and add exploratory testing
B. Add accessibility test type and include relevant test techniques at appropriate levels
C. Ignore accessibility as it’s not part of core features
D. Rely on unit testing for accessibility

Correct Answer: B
Explanation: Accessibility is a new test type and must be added to the test strategy.

Q1 – K2

Which statement is TRUE about applying test techniques?

A. Static techniques can only be used at system level
B. Any technique can be applied to any test type at any level
C. Dynamic techniques are always more effective
D. Test techniques are irrelevant in Agile

Answer: B


Q2 – K3

A performance-critical backend service is being developed. What's the best test combination?

A. Code review and exploratory testing
B. System-level performance testing using scripts
C. Manual user interface testing
D. Static analysis and load testing at unit level

Answer: B


Q3 – K3

You are planning testing for a project with strong user involvement and a focus on usability. What is the BEST choice?

A. Automated unit testing
B. Static code analysis
C. Manual acceptance tests involving users
D. Performance benchmarking

Answer: C


Q4 – K4

Your test strategy involves mostly automated tests. After several releases, customer-reported usability issues have increased. What is the BEST improvement?

A. Reduce automation and focus only on performance
B. Add manual usability testing with end-users
C. Automate usability tests
D. Increase static analysis scope

Answer: B


Q5 – K2

What is the primary output of choosing a test approach in the test strategy?

A. Test estimates
B. Detailed test cases
C. A tailored plan for levels, types, and techniques
D. Automation scripts

Answer: C

No comments:

Post a Comment

Lets Start...............

Cypress

Syllabus Q & A Set -1 Q & A Set -2