More on Quality Central Automated Incident Reports…

Chris Hesik sent me an email this morning offering to show me the tools he’s using to data mine the AIR’s in Quality Central. Of course I agreed, and we’ll meet on Monday.

In addition he sent the following out on an issue he found using this tool to another R&D engineer.

—–

I’ve been doing some data mining of the AIR reports in QC, and for the Cogswell RTM build, the most frequent stack trace reported (12 instances out of 191 total reports) is the stack trace shown in QC report 47921.

The error is a List Index out of Bounds and the top of the stack is:

[20031735]{rtl100.bpl  } Classes.TList.Get (Line 2992, "commonClasses.pas" + 2) + $A
[20031685]{rtl100.bpl  } Classes.TList.Error (Line 2961, "commonClasses.pas" + 1) + $14
[20031735]{rtl100.bpl  } Classes.TList.Get (Line 2992, "commonClasses.pas" + 2) + $A
[20031716]{rtl100.bpl  } Classes.TList.First (Line 2986, "commonClasses.pas" + 0) + $2
[20A450E3]{coreide100.bpl} EditorForm.TEditWindow.WindowActivate (Line 2487, "EditorForm.pas" + 3) + $5
[20A44E72]{coreide100.bpl} EditorForm.TEditWindow.WMActivate (Line 2411, "EditorForm.pas" + 2) + $B


It appears this is related to the change you made in revision 5882 of EditorForm.pas.  The List Index out of bounds occurs when calling EditWindowList.First if there are no items in EditWindowList.  I’m guessing the simple fix is to add a check to make sure that EditWindowList.Count>0, but I thought I would run this by you first.  Can you review the code and the stack trace and see if this is the correct fix?

—–

It’s a great example of using Quality Central and AIR’s from the development side. If I’m lucky, I can nudge him to blog about it.

I do suggest anyone logging an AIR from the IDE include their developer network information - that way we can contact you if needed.

5 Responses to “More on Quality Central Automated Incident Reports…”

  1. Sebastian Ledesma [Solidyne] Says:

    Can I use this feature in my applications? How? So I know when an app crash, the most frequent cases and so on.

    Thanks!

  2. Robert Love Says:

    The stack trace is generated using the JCL (Jedi Class Library) it is an open source library that you can use in your own applications to do the same type of thing.

    Codegear has taken it a step further by allowing you to submit the results via a web service to there QC database so they can mine the data.

  3. Uwe Schuster Says:

    You can download the latest JCL version from http://www.sf.net/projects/jcl and just to be correct the JCL = JEDI Code Library.

  4. Fabio Dell'Aria Says:

    Why not use EurekaLog ? :)

    http://www.eurekalog.com

  5. Chris Pattinson Says:

    Fabio, looks interesting. I’ll check it out. We have been talking about getting more information into our automated reports to help both QA reproduce and R&D fix issues.

Leave a Reply