Click to edit Master subtitle style

10/6/10

Heuristic Test Strategy Model

(James Bach Model)

By Nadeeshani Aththanagoda

10/6/10

Heuristic Test Strategy Model

A set of patterns for designing a test strategy.

what to think about when creating tests.

self-directed learningfully conscious testing among

professional testers.

10/6/10

What is it? resources, constraints, and other

forces

things that intend to

test

rules, values, and

sources

10/6/10

Con’t……Project Environment - Resources,

constraints, and other forces in the project that enable us to test

Product Elements- Things that intend to test

Quality Criteria- Rules, values, and sources that allow you as a tester to determine if the product has problems.

Test Techniques- Strategies for creating tests.

Perceived Quality- The result of testing

10/6/10

Heuristic Test Strategy Model categories

General Test TechniquesProject EnvironmentProduct ElementsQuality criteria categories

◦ Operational criteria◦ Development criteria

10/6/10

General Test Techniques1. Function Testing2. Domain Testing3. Stress Testing4. Flow Testing5. Scenario Testing6. Claims Testing7. User Testing8. Risk Testing9. Automatic Testing

10/6/10

1.Functional TestingTest what it can do Identify things that the product

can do Determine how you’d know if a

function was capable of working Test each function, one at a

time See that each function does

what it’s supposed to do and not what it isn’t supposed to do

10/6/10

2.Domain TestingDivide and conquer the data Look for any data processed by

the product Look at outputs as well as inputs Decide which particular data to

test with Consider combinations of data

worth testing together

10/6/10

3.Stress TestingOverwhelm the product Look for sub-systems and

functions that are vulnerable to being overloaded or “broken”.

Select or generate challenging data, or resource constraint conditions to test with: e.g.,

large or complex data structures, high loads, long test runs, many test cases, low memory conditions.

10/6/10

4.Flow TestingDo one thing after another Define test procedures or high

level cases that incorporate multiple activities connected end-to-end.

Don’t reset the system between tests.

Vary timing and sequencing, and try parallel threads.

10/6/10

5.Scenario Testing Test to a compelling story Begin by thinking about

everything going on around the product.

Design tests that involve meaningful and complex interactions with the product.

A good scenario test is a compelling story of how someone who matters might do something that matters with the product.

10/6/10

6.Clams TestingVerify every claim Identify reference materials that

include claims about the product (implicit or explicit).

Analyze individual claims, and clarify vague claims.

Verify that each claim about the product is true.

If you’re testing from an explicit specification, expect it and the product to be brought into alignment.

10/6/10

7.User Testing Involve the users Identify categories and roles of

users. Determine what each category

of user will do (use cases), how they will do it, and what they value.

Get real user data, or bring real users in to test.

Otherwise, systematically simulate a user

Powerful user testing is that which involves a variety of users and user roles, not just one.

10/6/10

8.Risk TestingImagine a problem, then look for it. What kinds of problems could

the product have? Which kinds matter most? How would you detect them if

they were there? Make a list of interesting

problems and design tests specifically to reveal them.

10/6/10

9.Automatic TestingRun a million different tests Look for opportunities to

automatically generate a lot of tests.

Develop an automated, high speed evaluation mechanism.

Write a program to generate, execute, and evaluate the tests.

10/6/10

Project Environment1. Customers2. Information3. Developer Relations4. Test Team5. Equipment & Tools6. Schedule7. Test terms8. Deliverables

10/6/10

Project EnvironmentCustomers-Anyone who is a client of the

test project. Information-Information about the

product or project that is needed for testing. Developer Relations-How you get

along with the programmers. Test Team-Anyone who will perform or

support testing.

10/6/10

Project EnvironmentEquipment & Tools -Hardware,

software, or documents required to testing Schedule-The sequence, duration, and

synchronization of project events‰ Test Items-The product to be tested

‰ Deliverables-The observable products of the test project

10/6/10

Product Elements1. Structure2. Function3. Data4. Platform5. Operations.6. Time.

10/6/10

Product ElementsStructure -Everything that comprises the

physical product. Function-Everything that the product

doesData- Everything that the product

processesPlatform-Everything on which the product

dependsOperations-How the product will be used.

Time-Any relationship between the product and time

10/6/10

Quality criteria categoriesA quality criterion is some requirement that defines what the product should be. By looking thinking about different kinds of criteria,

• Operational criteria• Development criteria

10/6/10

Operational criteria1. Capability2. Usability. 3. Security4. Scalability. 5. Performance6. Installability7. Compatibility.

10/6/10

Operational criteria

Capability-Can it perform the required functions?

Reliability-Will it work well and resist failure in all required situations?

Usability- How easy is it for a real user to use the product?

Security-How well is the product protected against unauthorized use or intrusion?

10/6/10

Operational criteriaScalability-How well does the

deployment of the product scale up or down? Performance-How speedy and

responsive is it? Installability-How easily can it be

installed onto its target platform(s)? Compatibility-How well does it work

with external components & configurations?

10/6/10

Development criteria1. Supportability.2. Testability.3. Maintainability4. Portability5. Localizability

10/6/10

Development criteriaSupportability-How economical will it

be to provide support to users of the product?

Testability-How effectively can the product be tested?

Maintainability-How economical is it to build, fix or enhance the product?

Portability-How economical will it be to port or reuse the technology elsewhere?

Localizability-How economical will it be to adapt the product for other places?

10/6/10

36 Letters……………..FDSFSCURA-general test

techniquesCIDTESTD-project environmentSFDPOT-product elementsCUUSSPICSTMPL-quality criteria

10/6/10

References

10/6/10

THANK YOU!