Eclipse Community Forums: Test and Performance Tools Platform (TPTP)

Home » Archived » Test and Performance Tools Platform (TPTP) » Bug prediction using past testing effort(Bug Prediction)

Show: Today's Messages :: Show Polls :: Message Navigator

Bug prediction using past testing effort [message #502426]

Tue, 08 December 2009 07:57

Aleem Alvi

Messages: 7
Registered: October 2009

Junior Member

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

Report message to a moderator

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

Tue, 08 December 2009 11:36

Paul Slauenwhite

Messages: 975
Registered: July 2009

Senior Member

Hi Aleem,
Unfortunately, TPTP does not maintain a mapping of source classes to
test classes. At best, we try to align our test plug-ins with functional
plug-ins for tests that do not traverse functional boundaries. For example,
here are the TPTP Test Project tests:

http://wiki.eclipse.org/TPTP_Test_Tools_Project_Tests

I would suggest also looking at the TPTP Testing Strategy:

http://www.eclipse.org/tptp/home/documents/process/TPTP_Test ing_Strategy.html

Paul
"Aleem Alvi" <akalvi@gmail.com> wrote in message
news:hfl0tj$v8r$1@build.eclipse.org...
> 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

Report message to a moderator

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

Tue, 08 December 2009 22:43

Aleem Alvi

Messages: 7
Registered: October 2009

Junior Member

Hi Paul,

Thanks for your reply.

I would like to know can we find the links between the test class and source code class by knowing that the test method (i.e. test case) in test class has a unique name?For example its name like "testAddFileAndFolder" there is a unique method in source class with the following name: "AddFileAndFolder". Further the object of source code class use in the test method of test class is unique and use for the particular unique class in source code.

OR

By analyzing the testing code.Find the code dependencies
then for each test code function we need to find the objects that it is touching creating. The objects we map them to the eclipse code itself we say these functions are testing this particular code.

These confirmation will help us for the data mining and getting the relationships between the source code class and test class.

I shall be very glad and appreciating your reply with hundred percent confirmation of any above method or new one which may help us to find the relationships between the source code class and test code classes.

Thanks and best regards,

Aleem Alvi

Report message to a moderator

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

Wed, 09 December 2009 11:12

Paul Slauenwhite

Messages: 975
Registered: July 2009

Senior Member

Unfortunately, there is no way to correlate test cases (e.g. JUnit test
methods) with functional code by name alone. Our testing process is not
sufficiently strict to make this correlation. You will have introspect the
code using static analysis or a profiler (e.g. TPTP Java Profiler).

Paul
"Aleem Alvi" <akalvi@gmail.com> wrote in message
news:hfmkq6$o3h$1@build.eclipse.org...
> Hi Paul,
>
> Thanks for your reply.
> I would like to know can we find the links between the test class and
> source code class by knowing that the test method (i.e. test case) in test
> class has a unique name?For example its name like "testAddFileAndFolder"
> there is a unique method in source class with the following name:
> "AddFileAndFolder". Further the object of source code class use in the
> test method of test class is unique and use for the particular unique
> class in source code.
>
> OR
>
> By analyzing the testing code.Find the code dependencies then for each
> test code function we need to find the objects that it is touching
> creating. The objects we map them to the eclipse code itself we say these
> functions are testing this particular code.
>
> These confirmation will help us for the data mining and getting the
> relationships between the source code class and test class.
>
> I shall be very glad and appreciating your reply with hundred percent
> confirmation of any above method or new one which may help us to find the
> relationships between the source code class and test code classes.
>
> Thanks and best regards,
>
> Aleem Alvi

Report message to a moderator

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

Thu, 17 December 2009 00:09

Aleem Alvi

Messages: 7
Registered: October 2009

Junior Member

Hi Paul,

Thank you for your reply. I would like to know that "has Eclipse source code class unique name? Means if we consider LaunchURL.java class available on following path

\\src\plugins\org.eclipse.help.ui\src\org\eclipse\help\ui\br owser\LaunchURL.java

THEN no other class in whole Eclipse source code base with "LaunchURL.java" name.

If yes then is this true also for the Automated test for example eclipse-Automated-Tests-2.1.zip is available on Eclipse archive including java test classes.

Thanks and best regards,

Aleem Alvi

Report message to a moderator

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

Thu, 17 December 2009 12:35

Paul Slauenwhite

Messages: 975
Registered: July 2009

Senior Member

Each source class should have a unique package name space. However, class
names can be reused.

Paul
"Aleem Alvi" <akalvi@gmail.com> wrote in message
news:hgbsrc$6sq$1@build.eclipse.org...
> Hi Paul,
>
> Thank you for your reply. I would like to know that "has Eclipse source
> code class unique name? Means if we consider LaunchURL.java class
> available on following path
>
> \\src\plugins\org.eclipse.help.ui\src\org\eclipse\help\ui\br
> owser\LaunchURL.java
>
> THEN no other class in whole Eclipse source code base with
> "LaunchURL.java" name.
>
> If yes then is this true also for the Automated test for example
> eclipse-Automated-Tests-2.1.zip is available on Eclipse archive including
> java test classes.
>
> Thanks and best regards,
>
> Aleem Alvi

Report message to a moderator

Previous Topic:	Application Server Starts, but nothing visible in Profiling Monitor view
Next Topic:	Help me prolong the time of IE enough entering the URLs in the address box!!!

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Apr 25 15:57:21 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter