1. To demonstrate to the developer and the customer that the software meets its requirements. For custom software, this means that there should be at least one test for every requirement in the user and system requirements document. For generic software products, it means that there should be tests for all of the system features, that will be incorporated in the product release. As discussed in chapter4, some system may have an explicit acceptance testing phase where the customer formally checks that the delivered system conforms to its specification.
2. To discover faults or defect in the software where the behavior of the software is incorrect, undesirable, or does not conform to its specification. Defect testing is concerned with rooting out all kinds undesirable system behavior such as system crashes, unwanted interactions with other systems, incorrect computations, and data corruption.
1. To demonstrate to the developer and the customer that the software meets its requirements. For custom software, this means that there should be at least one test for every requirement in the user and system requirements document. For generic software products, it means that there should be tests for all of the system features, that will be incorporated in the product release. As discussed in chapter4, some system may have an explicit acceptance testing phase where the customer formally checks that the delivered system conforms to its specification.
2. To discover faults or defect in the software where the behavior of the software is incorrect, undesirable, or does not conform to its specification. Defect testing is concerned with rooting out all kinds undesirable system behavior such as system crashes, unwanted interactions with other systems, incorrect computations, and data corruption.
need an explanation for this answer? contact us directly to get an explanation for this answer