As important, a software testing strategy provides a road map for the software developer, the quality assurance organization, and the customer- a road map that describes the steps to be conducted as part of testing, when these steps are planned and then undertaken, and how much effort, time, and resources will be required. Therefore any testing strategy must incorporate test planning, test case design, test execution, and resultant data collection and evaluation.
A software testing strategy should be flexible enough to promote the creativity and customization that are necessary to adequately test all large software-based systems. At the same time, the strategy must be rigid enough to promote reasonable planning and management tracking as the project progresses.
These approaches and philosophies are what we shall call strategy.
Different test methods begin to cluster into several distinct approaches and philosophies, which is called strategy.
Testing activity can be planned and conducted systematically; hence, to be very specific test case design methods are defined called as templates.
A number of software testing has been proposed in the literature. All provide the software developer with a template for testing and all have the following generic characteristics.
¨ Testing begins at module level or class or object level in object-oriented systems and works Outward toward the integration of the entire computer based system.
¨ Different techniques are appropriate at different points in time
¨ Testing is conducted by the developer of the software and, an independent test group for large projects
Testing and debugging are different activities, but debugging must be accommodated in any testing strategy
How should a strategy be?
¨ A strategy for software testing must accommodate low-level tests that are necessary to verify that a small source code segment has been correctly implemented as well as high-level tests that validate major customer requirements.
¨ A strategy must provide guidance for the practitioner and a set of milestones for the manager. Because the steps of the test strategy occur at a time when deadline pressure begins to rise, progress must be measurable and problems must surface.
Software testing is one element of a broader topic that is often referred to as verification and validation(V&V). Verification refers to the set of activities that ensure that software correctly implements a specific function. Validation refers to a different set of activities that ensure that the software that has been built is traceable to customer requirements.
Software testing is one element of a broader topic that is often referred to as verification and validation (V&V).
¨ Verification refers to the set of activities that ensure that correctly implements a specific function.
¨ Validation refers to a different set of activities that ensure that the software that has been built is traceable to customer requirements.
Boehm states like this.
Verification: "Are we building the product right"
Validation: "Are we building the right product?"
INTEGRATION TESTING PART ONE
INTEGRATION TESTING PART TWO
INTEGRATION TESTING PART THREE
INTEGRATION TESTING PART FOUR
INTEGRATION TESTING PART FIVE
INTEGRATION TEST STANDARDS
INTEGRATION TEST STANDARDS PART TWO
QUALITY ASSURANCE PART TWO
QUALITY ASSURANCE SQA
QUALITY OF DESIGN OF TEST CASE
QUALITY MANAGEMENT IN SOFTWARE TESTING
TOOLS FOR QUALITY MANAGEMENT
STATICAL QUALITY ASSURANCE
ISO APPROACH TO QUALITY TESTING