Quality Testing

Quality is delighting customers

please give me clear picture

Views: 86

Reply to This

Replies to This Discussion

Kishore, just search in the discussion link using my user id, i have replied to the same question a few days back....
Best wishes, Saju
kishore !
found the information myself for you....

Test Plan:

A document describing scope, approach, resources and schedule of intended test activities. It identifies amongst others, test items, the features to be tested, the testing tasks, who will do each task, the degree of tester independence,. The test environment, The test design techniques, the entry and exit criteria to be used and the rationale for their choice and any risks that requires contingency planning. It’s the record of the Test planning process

IEEE 829 Test Plan Template Contains the following :

• Test Plan Identifier
• Introduction
• Test Items
• Features to be tested
• Features not to be tested
• Approach
• Pass / Fail Criteria
• Suspension and resumption criteria
• Test Deliverables
• Test Tasks
• Environmental Needs
• Responsibilities
• Staffing and Training Needs
• Schedule
• Risks and Contingencies
• Approvals

Test Strategy:

A high level description of the test levels to be performed and the testing within those levels for an organization or program (one or more projects)

Test Approach:

The implementation of the test strategy for a specific project. It typically includes the decisions made based on the (test) projects goal and risk assessment carried out, starting points regarding the test process, the test design techniques to be applied, exit criteria and test types to be performed

More Ref : Foundations of Software Testing - ISTQB Certification
Upon accepting Mr.Kishore's comments, I would like to add my thoughts to this interesting query.

Test strategy is macro level while test methodology is micro level.

Test strategy is defined and implemented by management with alternative plans whereas selecting or defining suitable methodology for testing is done by test lead.

Test strategy is always to be defined based on assumptions before realizing required inputs. The strategy can be more precise with realized inputs. As far as strategy is concerned resources planning is crucial and the main challenge is that utilization of planned resources in case any delay happens on interdependencies.
When to start and which plan to be initiated is a part of test strategy. How to test and which method gives best result is part of test methodology.

Sometimes implementation of a plan can be suspended by management as part of their strategy.

More about testing and quality: www.mysdlc.webs.com/testing.htm


TTWT Magazine





© 2019   Created by Quality Testing.   Powered by

Badges  |  Report an Issue  |  Terms of Service