Software System Testing Process

Interpretation or Definition of various subjects used in this page.

  • “automation test script” means an executable file that is created out of a test automation tool.
  • “defect” means the condition in the software system, of being laid open to something undesirable or injurious.
  • “exploratory testing” means the activity of test design and test execution happening at the same time.
  • “objectives” means a set of end results that is intended out of activity undertaken.
  • “plan” means a document that describes the objectives, tactics and resource plan for the activity undertaken.
  • “resource plan” means a document that describes ‘when’ and ‘where’, ‘who’ shall do ‘what’?
  • “reviewer” means a person who performs the software document review activity
  • “software” means a piece of code that can be executed with a computer.
  • “software document” means a document that describes the software.
  • “software document review” or “document review” or “review” means an activity that aims at
    • evaluating the software document, or
    • identifying the condition in the software document, of being laid open to something undesirable or injurious.
  • a. “software system” means a collection of software and documents that describes the software.
  • b. “software tester” means a person who performs the software testing activity
  • “software testing” or “testing” means an activity that aims at
    • a. evaluating the software, or
    • b. identifying the condition in the software, of being laid open to something undesirable or injurious.
  • “tactics” means a set of procedures or set of maneuvers engaged in to achieve the objectives.
  • “test case” means a set of instructions that shall be followed during the activity of testing of software, and its expected behavior specified against each instruction or collection of instructions.
  • “test design” means the activity of creation of test cases.


    Review
  • Domain Expert(s) or persons equivalent to Domain Expert(s), known and referred as reviewer(s) shall review all the Software Documents that are developed.
  • The plan for the review activity, referred as “review plan” shall get created considering the following:
    • a. Software Requirements
    • b. Criticality of the Software Features
    • c. Complexity of the Software Features
  • The review plan shall be executed. The defects identified in the software documents are communicated to the appropriate designation. The status of execution shall be reported to all the relevant stakeholders of the review activity.


    Software Testing
  • Software Testers shall test all the Software that is developed.
  • The plan for the testing activity, referred as “test plan” shall get created considering the following:
    • a. Software Requirements
    • b. Criticality of the Software Features
    • c. Complexity of the Software Features
  • The test plan shall encompass the activity of creating test cases in case of any of the following conditions:
    • a. Repeatability of the testing activity is essential or critical.
    • b. Portability of test cases is essential or critical.
    • c. Test Cases along with Test Results are essential or critical, legally.
  • The test plan shall not encompass the activity of creating test cases and encompass only exploratory testing in case of any of the following conditions:
    • a. Repeatability of the testing activity is not essential and critical.
    • b. Portability of test cases is not essential and critical.
    • c. Test Cases along with Test Results are not essential and critical, legally.
  • The test plan shall get executed. The defects identified in the software are communicated to the appropriate designation. The status of execution shall be reported to all the relevant stakeholders of the testing activity.


    Automated Software Testing
  • A set of test cases shall get identified as a candidate for automation if and only if it warrants multiple rounds of execution where estimated cost of automation is less than the estimated cost that will not be incurred upon automation.
  • The plan for the test automation, referred as “test automation plan”, shall get prepared considering the above point.
  • The test automation plan shall get executed. The status of execution shall be reported to all the relevant stakeholders of the testing activity.
  • For the purpose of test automation, there shall exist a reference database for the application under test, based on which the automation test scripts are created and executed.
  • style="display:block"
    data-ad-client="ca-pub-9945402454384428"
    data-ad-slot="3540880857"
    data-ad-format="autorelaxed">