Testing in itself cannot ensure the quality of software. All testing can do is give you a certain level of assurance (confidence) in the software. On its own, the only thing that testing proves is that under specific controlled conditions, the software functioned as expected by the test cases executed.
difference between QA and testing:
TESTING means “Quality Control”; and
QUALITY CONTROL measures the quality of a product; while
QUALITY ASSURANCE measures the quality of processes used to create a quality product.
The Mission of Testing:
In well-run projects, the mission of the test team is not merely to perform testing, but to help minimize the risk of product failure. Testers look for manifest problems in the product, potential problems, and the absence of problems. They explore, assess, track, and report product quality, so that others in the project can make informed decisions about product development. It's important to recognize that testers are not out to "break the code." We are not out to embarrass or complain, just to inform. We are human meters of product quality.
The test policy characterises the organisation’s philosophy towards software testing. This would incorporate statements to ensure compliance with standards such as ISO 9001, ISO 12207 and IEEE 730. ISO 9001 provides only a very high level requirement that suppliers perform testing as part of verification and document it. At this level ISO 12207 defines the requirement for specific verification and validation processes to support the primary processes of development, maintenance, etc.
IEEE 730 requires the production of both a Software Verification and Validation Plan (and corresponding Report) and the documentation of any other tests (presumably those performed by the developers), but appears to be superfluous, from a testing point of view, if ISO 9001 and ISO 12207 are used.
A Testing Policy is management’s definition of testing a department. A Testing Policy involves the following criteria.
1)Definition of Testing
2) Testing System
3) Evaluation
4) Standards
RELATED POSTSOFTWARE QUALITY ASSURANCE AND CONTROL
SOFTWARE QUALITY AND COST ASPECT
STABLE PROCESS OF SOFTWARE TESTING
STABLE PROCESS OF SOFTWARE TESTING PART TWO
DEFECTS IN SOFTWARE TESTING
REDUCTION OF DEFECTS IN SOFTWARE TESTING
SOFTWARE TESTING AND EFFECTING FACTORS
SCOPE OF SOFTWARE TESTING
TESTING LIFE CYCLE PART ONE
TESTING LIFE CYCLE PART TWO
TESTING LIFE CYCLE PART THREE
SOFTWARE TESTING AND CONSTRAINTS WITH IN IT
TESTING CONSTRAINTS PART TWO
LIFE CYCLE TESTING
TEST METRICS
Independent Software Testing
Test Process
Testing verification and validation
Functional and structural testing
Static and dynamic testing
V model testing
Eleven steps of V model testing
Structural testing
Execution testing technique
Recovery Testing technique
Operation testing technique
Compliance software testing technique
Security testing technique
No comments:
Post a Comment