Testing Process
- 1. TOPIC TESTING PROCESS Pandey Abhishek TY Bsc I.T. (A)
- 2. INTRODUCTION SOFTWARE TESTING is defined as an activity to check whether the actual results match the expected results and to ensure that the software system is defect free. It involves execution of a software component or system component to evaluate one or more properties of interest. Software testing also helps to identify errors, gaps or missing requirements in contrary to the actual requirements. It can be either done manually or using automated tools.
- 3. Process Defining Test Policy Defining Test Strategy Preparing test plan Establishing testing Objective for be achieved Designing test scenarios & Test cases Writing /Rewriting test cases Defining Test data Creation of test bed Executing test cases Test result Test Result analysis Retesting / Regression testing
- 4. .Defining test policy • Test policy are defined by senior management of the organization • Test policy at organization level define the • A Test Policy is a high level document and is at the top of the hierarchy of the Test Documentation structure .Test Strategy • A strategy plan for defining the testing approach, what you want to accomplish and how you are going to achieve it. This document removes all uncertainty or vague requirement statements with a clear plan of approach for achieving the test objectives. Test Strategy is one of the most important documents for the QA team. .Test plan • A document describing the scope, approach, resources and schedule of intended test activities. It identifies amongst others test items, the features to be tested, the testing tasks, who will do each task, degree of tester independence, the test environment, the test design techniques and entry and exit criteria to be used, and the rationale for their choice, and any risks requiring contingency planning. It is a record of the test planning process.
- 5. .Testing objective • Test objective measure the effectiveness and efficiency of a testing process • They also define test achievements that they plan . • Testing objective must be SMART (Specific, Measurable, Agreed upon, Realistic, and Time Bound) .Scenarios & Case • A test scenario represent user scenario which act as a framework for defining test cases, • Each transaction in a test scenario eventually becomes a test case. .Writing & Reviewing • Writing & reviewing test cases along with test scenarios and updating requirement traceability matrix accordingly are the task done by senior testers or test leads for the project
- 6. .Test data • Test data may be defined on the basis of boundary value analysis • Guessing error, equivalence partitioning and state transition • Test data must include valid as invalid set of data along with some special values generated from error guessing. .Test bed • Test bed define some of the assumptions in a test plan which may induce certain risks of testing .Test cases • Execution of current test cases with the test data defined for testing the s/w involves applying test cases as well as test data and trying to get the current results.
- 7. . Test result • Logging results of testing in test log is the last part of the testing iteration . . Test re analysis • Examining test results and analysis may lead to interpretation of software in terms of capabilities and weakness. . Retesting/Regression • Retesting is done to find out whether the defects declared as fixed and verified by the development team are really fixed or not . • Regression testing is done to confirm that the changed part has not affected (in a negative way) any other parts of s/w, which were working earlier.