Re: [m2] Surefire w/TestNG
;) /Kaare On 06/01/06, Srepfler Srgjan <[EMAIL PROTECTED]> wrote: > I have tried to put in touch a person from this list (Kaare Nilsen) that > had made a "80% functional" test-ng prototype plugin with Cedric Beust > of TestNG and they exchanged these mails, as they were only between the > four of us perhaps you'd like to follow up on it: > > Cedric: > > Hi Srepfler (and Kaare and Andy) and thanks for the note. > > Kaare: sorry you had such a hard time with our code base. I wasn't > even aware you were working on that, I would have been happy to help > you. And I agree that our dual annotation code base is not the simplest > and interestingly, I have been thinking of ways to revamp it these past > days. Quite a coincidence. > > Finally, Andrew is in copy because he's the author of the Maven 1.1 > plug-in and he's currently working on a 2.0 version. Andrew, maybe you > could benefit from Kaare's work so far? > > Kaare: > > Hi. > > First I would like to balance the sheet by saying that I think testNg > is a very well put together from an user perspective, and I have > really nothing bad to say about that. > But from a "plugin" perspective my main critic is that i can't seem to > find a clean interface for invoking it. > With that said. I would very much like the plugin to get finished, but > my effort is at the time beeing directed to the aspectJ plugin for m2 > and i really do not have time to find out what part of the annotation > codebase that conflicts with maven. > > Btw: would it not be a good idea to get testNG jars uploaded to ibiblio ? > > Cedric: > > Hi Kaare, > > No need to apologize :-) > > When a project grows big enough, you can't really like 100% of its > source code any more, no matter how hard you try, so your criticism is > well taken. > > Could you be a bit more specific as to what problems you encountered? > It might be a learning experience for me and the people in CC as well, > and I'll be more than happy to do my best and make sure that writing a > Maven 2 plug-in for TestNG will be as effortless as possible for whoever > ends up stepping up to the plate... > > Andy: > > Putting the TestNG jars on Ibiblio would be excellent. I started down > this path, but lost interest when I saw the process... > > Do you mind sharing what you've done thus far on the plug-in- perhaps I > can finish it? > > Thank you!! > > Kaare: > > But of course > > Cedric: > > Just wanted to let you know that I completely revamped our annotation > support. Everything is working and we're back at 100% tests now. I > still need to delete a few files and do some renaming, but the dual > annotation support is much cleaner now. I'll be happy to write up a > quick design overview (should take a few paragraphs) if you're > interested. > > > Having said that, I realized I never really asked you why you > needed a better understanding of that part of our codebase for your > Maven 2 plug-in... I am not familiar with the Maven plug-in API, but I > have always been under the impression that interfacing with TestNG > requires nothing more than being able to create a TestNG() object, set > various parameters, add a listener and call run(). > > > Care to share your findings? > > Kaare: > > Sure.. > > The problem does not really occur when everything works as expected, > it is when problems occur and one needs to dig into how things work, > and what classes one needs to provide new implementation of fixes for. > It is very popssible that i have approached this plugin in a very > wrong way, but basicly what happens is that I do not suspect the class > in a project containing the main method to be the public api but more > a wrapper for the project to use the api. So the first thing i usually > do is to read the main method and see how things are wired together > and how the command line args are parsed to parameters to the api. > Then i try to emulate the main method. > Right now (since it has been a while since i stopped the attemt) I > really do not remember why I abondoned this approach, and tried > another solution, but i suspect it had something to to with the > annotations not working. > What i could try again with the new versions released is to try the > first approach again, and try to "copy" the privateMain method > replacing the commandline args with plugin configuration params and > then see what happens. > But with all that said, the testng plugin should really be integrated > into the surefire plugin to get it to run as an equal to junit, but i > would settle for an own plugin for now. > > -- > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Surefire w/TestNG
I have tried to put in touch a person from this list (Kaare Nilsen) that had made a "80% functional" test-ng prototype plugin with Cedric Beust of TestNG and they exchanged these mails, as they were only between the four of us perhaps you'd like to follow up on it: Cedric: Hi Srepfler (and Kaare and Andy) and thanks for the note. Kaare: sorry you had such a hard time with our code base. I wasn't even aware you were working on that, I would have been happy to help you. And I agree that our dual annotation code base is not the simplest and interestingly, I have been thinking of ways to revamp it these past days. Quite a coincidence. Finally, Andrew is in copy because he's the author of the Maven 1.1 plug-in and he's currently working on a 2.0 version. Andrew, maybe you could benefit from Kaare's work so far? Kaare: Hi. First I would like to balance the sheet by saying that I think testNg is a very well put together from an user perspective, and I have really nothing bad to say about that. But from a "plugin" perspective my main critic is that i can't seem to find a clean interface for invoking it. With that said. I would very much like the plugin to get finished, but my effort is at the time beeing directed to the aspectJ plugin for m2 and i really do not have time to find out what part of the annotation codebase that conflicts with maven. Btw: would it not be a good idea to get testNG jars uploaded to ibiblio ? Cedric: Hi Kaare, No need to apologize :-) When a project grows big enough, you can't really like 100% of its source code any more, no matter how hard you try, so your criticism is well taken. Could you be a bit more specific as to what problems you encountered? It might be a learning experience for me and the people in CC as well, and I'll be more than happy to do my best and make sure that writing a Maven 2 plug-in for TestNG will be as effortless as possible for whoever ends up stepping up to the plate... Andy: Putting the TestNG jars on Ibiblio would be excellent. I started down this path, but lost interest when I saw the process... Do you mind sharing what you've done thus far on the plug-in- perhaps I can finish it? Thank you!! Kaare: But of course Cedric: Just wanted to let you know that I completely revamped our annotation support. Everything is working and we're back at 100% tests now. I still need to delete a few files and do some renaming, but the dual annotation support is much cleaner now. I'll be happy to write up a quick design overview (should take a few paragraphs) if you're interested. Having said that, I realized I never really asked you why you needed a better understanding of that part of our codebase for your Maven 2 plug-in... I am not familiar with the Maven plug-in API, but I have always been under the impression that interfacing with TestNG requires nothing more than being able to create a TestNG() object, set various parameters, add a listener and call run(). Care to share your findings? Kaare: Sure.. The problem does not really occur when everything works as expected, it is when problems occur and one needs to dig into how things work, and what classes one needs to provide new implementation of fixes for. It is very popssible that i have approached this plugin in a very wrong way, but basicly what happens is that I do not suspect the class in a project containing the main method to be the public api but more a wrapper for the project to use the api. So the first thing i usually do is to read the main method and see how things are wired together and how the command line args are parsed to parameters to the api. Then i try to emulate the main method. Right now (since it has been a while since i stopped the attemt) I really do not remember why I abondoned this approach, and tried another solution, but i suspect it had something to to with the annotations not working. What i could try again with the new versions released is to try the first approach again, and try to "copy" the privateMain method replacing the commandline args with plugin configuration params and then see what happens. But with all that said, the testng plugin should really be integrated into the surefire plugin to get it to run as an equal to junit, but i would settle for an own plugin for now. -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Surefire w/TestNG
Some talk. http://jira.codehaus.org/browse/MSUREFIRE-23 On 1/6/06, Jason Dillon <[EMAIL PROTECTED]> wrote: > Any status on support for TestNG from Surefire w/Maven2? > > --jason > This email and any attachment(s) thereto, are intended for the use of > the addressee(s) named herein and may contain legally privileged and or > confidential information under applicable law. If you are not the > intended recipient of this e-mail, you are hereby notified any > dissemination, distribution or copying of this email, and any attachment(s) > thereto, is strictly prohibited. If you have received this communication > in error, please notify the sender at 415-281-2200 or via return e-mail at > [EMAIL PROTECTED] and permanently delete the original copy and > any copy of any e-mail, and any printout thereof. Thank you for your > cooperation. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] Surefire w/TestNG
Any status on support for TestNG from Surefire w/Maven2? --jason This email and any attachment(s) thereto, are intended for the use of the addressee(s) named herein and may contain legally privileged and or confidential information under applicable law. If you are not the intended recipient of this e-mail, you are hereby notified any dissemination, distribution or copying of this email, and any attachment(s) thereto, is strictly prohibited. If you have received this communication in error, please notify the sender at 415-281-2200 or via return e-mail at [EMAIL PROTECTED] and permanently delete the original copy and any copy of any e-mail, and any printout thereof. Thank you for your cooperation. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
