Software System Testing Process 2003

Software System Testing Process 2003 ISST Copyright © 2003 International Society of Software Testing 1 of 4 All Rights Reserved International Society of Software Testing Software System Testing Process 2003 Software System Testing Process 2003 ISST Copyright © 2003 International Society of Software Testing 2 of 4 All Rights Reserved Preamble (1) To make better provision for the planning and execution of Software Testing, the standard is enacted as follows: Title (2) This standard may be called as the “Software System Testing Process 2003”. Interpretation or Definition (3) In this standard, unless the context otherwise requires – a. “software” means a piece of code that can be executed with a computer. b. “software document” means a document that describes the software. c. “software system” means a collection of software and documents that describes the software. d. “software document review” or “document review” or “review” means an activity that aims at i. evaluating the software document, or ii. identifying the condition in the software document, of being laid open to something undesirable or injurious. e. “software testing” or “testing” means an activity that aims at i. evaluating the software, or ii. identifying the condition in the software, of being laid open to something undesirable or injurious. f. “reviewer” means a person who performs the software document review activity g. “software tester” means a person who performs the software testing activity h. “plan” means a document that describes the objectives, tactics and resource plan for the activity undertaken. i. “objectives” means a set of end results that is intended out of activity undertaken. j. “tactics” means a set of procedures or set of maneuvers engaged in to achieve the objectives. k. “resource plan” means a document that describes ‘when’ and ‘where’, ‘who’ shall do ‘what’? l. “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. m. “test design” means the activity of creation of test cases. Software System Testing Process 2003 ISST Copyright © 2003 International Society of Software Testing 3 of 4 All Rights Reserved n. “exploratory testing”1 means the activity of test design and test execution happening at the same time. o. “defect” means the condition in the software system, of being laid open to something undesirable or injurious. Review (4) Domain Expert(s), known and referred as reviewer(s) shall review all the Software Documents that are developed. (5) The plan for this review activity, referred as “review plan” is created considering the following: a. Software Requirements b. Criticality of the Software Features c. Complexity of the Software Features (6) 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 (7) Software Testers shall test all the Software that is developed. (8) The plan for this testing activity, referred as “test plan” is created considering the following: a. Software Requirements b. Criticality of the Software Features c. Complexity of the Software Features (9) The test plan shall encompass the activity of creating test cases in case of 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. (10) The test plan shall not encompass the activity of creating test cases and encompass only exploratory testing in case of 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. 1 Reference: http://www.satisfice.com/articles/what_is_et.htm Software System Testing Process 2003 ISST Copyright © 2003 International Society of Software Testing 4 of 4 All Rights Reserved (11) The test plan shall be 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.