1 / 9

Fundamental Software Testing Process

http://qatestlab.com//nThe fundamental test process includes such parts

qatestlab
Télécharger la présentation

Fundamental Software Testing Process

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Fundamental Software Testing Process

  2. Fundamental Test Process The fundamental test process includes such parts: Office in Ukraine Phone: +38(044)501-55-38 E-mail: contact (at) qa-testlab.com Address: 154a, Borschagivska str., Kiev, Ukraine http://qatestlab.com/

  3. Test Planning The test plan should clarify in what way the test strategy and test plan apply to the software under test. It should contain identification of all exceptions to the test strategy and of all software with which the software under test will interact during accomplishment of test (for example, drivers and stubs). Office in Ukraine Phone: +38(044)501-55-38 E-mail: contact (at) qa-testlab.com Address: 154a, Borschagivska str., Kiev, Ukraine http://qatestlab.com/

  4. Test Specification Test cases should be designed with the help of test case design methods. Office in Ukraine Phone: +38(044)501-55-38 E-mail: contact (at) qa-testlab.com Address: 154a, Borschagivska str., Kiev, Ukraine http://qatestlab.com/

  5. Test Execution Undoubtedly every test case should be executed. Office in Ukraine Phone: +38(044)501-55-38 E-mail: contact (at) qa-testlab.com Address: 154a, Borschagivska str., Kiev, Ukraine http://qatestlab.com/

  6. Test Recording The test records for all test cases should anyway record the identities and versions of the software under test and the test specification. The actual outcome should be recorded and compared against the expected outcome. Any difference found should be logged and analyzed to establish where its cause lies and the earliest test activity that should be repeated. Office in Ukraine Phone: +38(044)501-55-38 E-mail: contact (at) qa-testlab.com Address: 154a, Borschagivska str., Kiev, Ukraine http://qatestlab.com/

  7. Checking for Test Completion The test records should be checked against the previously specified test completion criteria. If these criteria are not met, the earliest test activity that must be repeated in order to meet the criteria should be identified and the test process should be restarted from that point. Office in Ukraine Phone: +38(044)501-55-38 E-mail: contact (at) qa-testlab.com Address: 154a, Borschagivska str., Kiev, Ukraine http://qatestlab.com/

  8. Fundamental Test Process Since the purpose of software test should be to find defects, a successful test is one that detects a defect. This is counter-intuitional, because defects postpone progress: a successful test is one that may cause postpone. The successful test detects such defects which, if not found in time, may be many times more high-priced to correct. Completion or exit criteria are used to determine when testing (at any test phase) is complete. Office in Ukraine Phone: +38(044)501-55-38 E-mail: contact (at) qa-testlab.com Address: 154a, Borschagivska str., Kiev, Ukraine http://qatestlab.com/

  9. Office in Ukraine Phone: +38(044)501-55-38 E-mail: contact (at) qa-testlab.com Address: 154a, Borschagivska str., Kiev, Ukraine http://qatestlab.com/ Thank You !

More Related