Browse Prior Art Database

Method and System for Improving Productivity of Defect Fixing by Identifying required Test Assets

IP.com Disclosure Number: IPCOM000202406D
Publication Date: 2010-Dec-15
Document File: 2 page(s) / 47K

Publishing Venue

The IP.com Prior Art Database

Abstract

A method and system for improving productivity of defect fixing by identifying required test assets is disclosed. The method involves learning from previous similar interactions between development and testing teams, and prompting the tester to be pro-active in providing the necessary and required information upfront, mostly at the time of opening a defect.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 51% of the total text.

Page 01 of 2

Method and System for Improving Productivity of Defect Fixing by Identifying required Test Assets

Disclosed is a method and system for improving productivity of defect fixing by identifying required test assets.

The success of any testing cycle is proportional to the number of defects uncovered and subsequent fixes. A very essential part of the testing cycle is opening defects by providing the correct, exact and complete details required to a developer by tester. Therefore, to have a successful testing cycle, a defect tracking system may be employed to learn from previous similar interactions between development and testing teams. The defect tracking system then prompts the tester to be pro-active in providing the necessary and required information upfront, mostly at the time of opening the defect.

Typically, during a testing cycle a defect reporting exercise is generated. A common defect reporting exercise may involve some common criteria such as,

Affected testcases: Testcase1, Testcase2, etc

Affected testsuite: Testsuite1

Platform: AIX*

Database: DB2*

App Server: WAS* 7

Behavior: Java** Null pointer exception

Expected Behavior: Success

Component: Component1

These details may be followed by a textual description of the method followed to identify the defective behavior and analysis indicating the reason for a defective behavior. Such information may be followed by a comment on the location of the test assets, such as test cases, logs, environment settings, etc. The information may be targeted at helping the development team to recreate or debug the problem. Now, when there is a discrepancy in the defect description or the test assets provided, the developer adds a comment to the defect tracking system asking for these requirements. The process may include many iterations till the development team receives all the required artifacts and answers to its deciding questions.

In this method, initially, a tester decides the key factors about an environment and a testcase. Then, the defect tracking system searches for earlier defects based...