Eclipse Community Forums: Test » Bug prediction using past testing effort

Home » General (non-technical) » Test » Bug prediction using past testing effort (We have repilcated the effort of Nachi Nagappan paper with Eclipse platform with respect to Churn, Complexity and dependency metrics. Now we wouldllike to add one more thing that is the testing hist)

Bug prediction using past testing effort [message #502169]

Sun, 06 December 2009 16:25

Eclipse User

Hi all,

I would like to say that we are doing the bug prediction using testing efforts. For measuring testing effort from version 2.1 of eclipse to version 3.0. We found difficulty to
1) Map the source code classes used for testing and create there test classes.
Description: we have sort out the test by assert() method and find the list of testing classes and from promise data set given by Nachi Nagappan we have tried to get the map but not successful.

2) we try to map test class and source classes with in eclipse version 2.1 and 3.0. Further check that how much number of the classes are used in both version similar.

Kindly any one can help to solve the accurate and true mapping of source class and test classes. Just we need to know that our approach has missing some thing or not.

Your help will be highly appreciated.
Regards,

Aleem Alvi
PhD student
Queens University
Kingston, Canada

Re: Bug prediction using past testing effort [message #502306 is a reply to message #502169]

Mon, 07 December 2009 11:18

Eclipse User

I've updated the description of this forum to make it clear that it is not related to Eclipse Testing. You should ask your questions in the Eclipse Projects > Test and Performance Tools Platform forum instead.

Previous Topic:	Testing the quote service
Next Topic:	Bug prediction using past testing effort

Goto Forum:

-=] Back to Top [=-

Current Time: Wed Mar 19 09:33:53 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter