Browse Prior Art Database

Automatic Problem Determination System via Stacktrace and Unit Test

IP.com Disclosure Number: IPCOM000200366D
Publication Date: 2010-Oct-08
Document File: 5 page(s) / 87K

Publishing Venue

The IP.com Prior Art Database

Abstract

In product’s testing, testers need to do problem analyses before opening defects to product, they need to identify target component to which defect is opened. What they mainly count on is exception stack trace. Normally, current solution is that testers analyze stack trace by themselves and identify problem component manually. Drawback of such known solution is that whether testers can identify root cause of the problem quickly, whether they can open defect to right component at once, that mostly depends on tester’s knowledge base and experience. If the tester is a new hand, he will open the defect to the component which contains the first API in the top of exception stack, but probably, that isn’t the root cause at all, then the defect will be redirected through kinds of components, and need long time to get resolved. Disclosed here is an automatic problem determination system via stacktrace and unit test to help identify the actual root cause of the problem quickly.

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

Page 01 of 5

Automatic Problem Determination System via Stacktrace and Unit Test

1. Background

In product's testing, testers need to do problem analyses before opening defects to product , they need to identify target component to which defect is opened. What they mainly count on is exception stack trace. Normally, current solution is that testers analyze stack trace by themselves and identify problem component manually. Drawback of such known solution is that whether testers can identify root cause of the problem quickly,

whether they can open defect to right component at once

                                                               , that mostly depends on tester' s knowledge base and experience. If the tester is a new hand, he will open the defect to the component which contains the first

API in the top of exception stack

                     , but probably, that isn't the root cause at all, then the defect will be redirected through kinds of components, and need long time to get resolved.

So we need some way to facilitate guy to do automatic problem determination which can increase whole team's efficiency .

new way should be able to be used by all people easily.

Prior Art Comparison:

(1)SYSTEM AND METHOD OF FAULT DETECTION, DIAGNOSIS AND PREVENTION FOR COMPLEX computing system, Maharaj Mukherjee, 2009,
This invention is to set up diagnostic repository and specific for object oriented. While our invention isn't limit to object oriented system.
(2)Method and apparatus for graphically analzying a log-file , Stephen Gregory Eick et al, 1998 This invention is to analyze log file graphically. It's different with our invention obviously.
(3)Identification of uninformative function names in call-stack traces , Natwar Modani et al, 2009
This invention is to do problem determination by identifying uninformative function names through matching call -stack trace and some additional counting & threshhold method. It's not the same scope with our invention.
(4)Diagnostic methodology for debugging integrated software , Roger Bodamer, 2000
This invention is mainly for integrated software, to simulate one software to isolate the problem to specific software. It's not the same scope with our invention.
(5)

Automated Problem Determination Using Call

-Stack Matching,


This publication is used stack trace matching technology to do problem determination. While our invention is to leverage existing unit test suite to do problem determination.
(6)Techniques for automatic software error diagnostics and correction, Sashikanth Chandrasekaran,2008
This invention uses auto code path switch, diagnostics feature enable, error information match to implement auto diagnostic. While

1

And this


Page 02 of 5

our invention use API (auto get based on stack trace) related UT to identify the root cause.
( 7)Process for making software diagnostics more efficient by leveraging existing content, human filtering and automated diagnostic tools , William Pugh et al, 2008
This invention uses stack trace ma...