Chapter 2

z
Test Planning
 z
Introductions

“Planning must take place as early as possible in the

software life cycle, as lead times must be considered for
implementing the test program successfully.”
 z
Test Planning Activities

Goals of the testing Approaches to Considerations related

effort determining the test to data, environments,
strategy and the software itself.
 z
Early Planning

Allows testing To be
• Schedule • Estimated.
• Budget • Approved.
• Incorporated.

Estimation is So can be
• Monitored • Revised.
• Compared • Expectation
Managed.
 z
Test Planning requires

Understan Estimate
In order to Acquire
d Resource

Corporate Adapt/Suggest Necessary Testing Tools

culture Improvement buy-in

Testing
Software

SW Dev To Process as
Hire personnel Testing
Process necessary.
Hardware
z
Test Strategy

Design Must consider:

• Risks
• Resource
• Time
• Budget Constraint

Resource Include:
• Number of personnel
• Types of expertise
• Roles & Responsibilities
• Schedules & Budget
z
Testing Effort

 Definition: Expenses for tests.

 Estimated by using ratio methods & past efforts of

similar scope.

 Proper estimation allows effective test team.

 z
6: Understand the task at hand & related
testing goals

 Testing, in general, is conducted to verify that software meets specific

criteria and satisfies the requirements of the end user.

 Function correctly under all circumstances and will meet the defined
requirements, satisfying the end users.

 Goal is the detection and removal of defects in the software.

 Through inspections, walk-throughs, testing, or

excellent software development practices.
 z
Correctly Function Program

 Given valid input, the program produces the correct output as defined by
the specifications.

 Given invalid input, the program correctly and gracefully rejects the input
(and, if appropriate, displays an error message).

 The program doesn't hang or crash, given either valid or invalid input.

 The program keeps running correctly for as long as expected.

 The program achieves its functional and nonfunctional requirements.

z
Test Strategies

 Definition: Help achieve testing goals in the most

effective manner.

 Prioritize defects to meet deadlines.

 Understanding the task at hand, its scope, and its

associated testing goals are the first steps in test
planning.
z
How to achieving testing goal?

1. Test manager take all documented requirement

2. Develop a test plan, including testing strategy

3. Break down requirement features by features

4. Task testing team with design & develop test

procedures
z
How team want to understand
component part of testing goal?

1. Understanding the system: Functional & Non-

functional requirements

2. Early involvement: All team members involved during

system’s inception phase.

3. Understanding corporate culture& process: Adapt &

suggest improvement needed.
z

4. Scope of implementation: Scale the testing scope

5. Testing expectations: Management expectation,

testing customer expect?

6. Lesson learned: Previous testing effort, determining

strategies & setting realistic expectations.
z

7. Level of effort: Scale of effort to develop the system.

Hiring developer, estimation.

8. Type of solution: Complex solution / cost-effective

solution

9. Technology Choices: Technology selected for

implementation, potential issues? Architecture
system will use? Apps / web / desktop?
z

10. Budget: Implementing including testing? Types of

testing possible?

11. Schedule: Time allocated for developing & testing.

Deadlines

12. Phased solution: Many release with incremental

features? Big release?