junit-remote-discuss Mailing List for JUnit Remote
Status: Beta
Brought to you by:
totten_s
Menu
▾
▴
junit-remote-discuss — JUnit Remote General Discussion
You can subscribe to this list here.
| 2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(4) |
Nov
|
Dec
|
|
From: Steven S. <sta...@oc...> - 2009-10-21 20:05:07
|
Dan Keshet wrote: > Hi Steve, > > Thank you for your wonderful project. Thank you for the kind words! I'm glad this has been useful for you. > I'm sorry, I don't have enough time to do it the right way, although I > agree that an XML format would be preferable. I've attached the diff of > what I'm using in my project for now against the main project: it just > replaces the message with a stack trace. It's not very clean, though. No problem. Looking at your changes, I might do a little digging tonight - its not ideal, but what you are suggesting might not be a bad solution. > I'll stay subscribed to this list and If I get a chance to circle back > and do this in a nicer way, I'll let you know. > > In addition to the stack trace change, I have also made the @Remote tag > inherited by default. I have a test class that all my remote tests are > already inheriting from. Nice catch! I'll make sure to get this integrated. Cheers, -- Steven Stallion Senior Software Engineer Object Computing, Inc. http://www.ociweb.com |
|
From: Dan K. <dk...@qc...> - 2009-10-21 18:53:22
|
Hi Steve, Thank you for your wonderful project. I'm sorry, I don't have enough time to do it the right way, although I agree that an XML format would be preferable. I've attached the diff of what I'm using in my project for now against the main project: it just replaces the message with a stack trace. It's not very clean, though. I'll stay subscribed to this list and If I get a chance to circle back and do this in a nicer way, I'll let you know. In addition to the stack trace change, I have also made the @Remote tag inherited by default. I have a test class that all my remote tests are already inheriting from. Dan On Wed, Oct 21, 2009 at 12:29 PM, Steven Stallion <sta...@oc...>wrote: > Dan Keshet wrote: > > How much work would it be to include stack traces on failures in remote > > tests? Any work started on this? Any pointers on where I could start? > > Hello Dan, > > Thanks for your interest in the project! Unfortunately, due demands on > other funded projects, I have not had any time to complete any work on > the project since the initial release. > > If you are interested in adding support for remote stack traces that > would be very helpful! Probably the best place to get started is to look > at how the RemoteTestResult class is used. > > Up until this point, the messages passed back to remote client has been > simple text in the HTTP response. What I would like to see added first > is to convert all responses to an XML format. Once that is done, it > should be trivial to add an additional element which contains the stack > trace output (i.e. you could simply dump the results of a > e.printStackTrace() call). > > To get started, you can check out the junit-remote trunk from > SourceForge, see: https://sourceforge.net/projects/junit-remote/develop > > Once you have completed your changes, please prepare a diff (svn diff > should be just fine) and respond to the list. I'll then review and > integrate your changes. > > Of course, if you would like to become a regular contributor to the > project, once you have a commit under your belt I would be more than > happy to add you to the project. > > Cheers, > > -- > Steven Stallion > Senior Software Engineer > Object Computing, Inc. > http://www.ociweb.com > |
|
From: Steven S. <sta...@oc...> - 2009-10-21 17:30:03
|
Dan Keshet wrote: > How much work would it be to include stack traces on failures in remote > tests? Any work started on this? Any pointers on where I could start? Hello Dan, Thanks for your interest in the project! Unfortunately, due demands on other funded projects, I have not had any time to complete any work on the project since the initial release. If you are interested in adding support for remote stack traces that would be very helpful! Probably the best place to get started is to look at how the RemoteTestResult class is used. Up until this point, the messages passed back to remote client has been simple text in the HTTP response. What I would like to see added first is to convert all responses to an XML format. Once that is done, it should be trivial to add an additional element which contains the stack trace output (i.e. you could simply dump the results of a e.printStackTrace() call). To get started, you can check out the junit-remote trunk from SourceForge, see: https://sourceforge.net/projects/junit-remote/develop Once you have completed your changes, please prepare a diff (svn diff should be just fine) and respond to the list. I'll then review and integrate your changes. Of course, if you would like to become a regular contributor to the project, once you have a commit under your belt I would be more than happy to add you to the project. Cheers, -- Steven Stallion Senior Software Engineer Object Computing, Inc. http://www.ociweb.com |
|
From: Dan K. <dk...@qc...> - 2009-10-21 16:44:58
|
How much work would it be to include stack traces on failures in remote tests? Any work started on this? Any pointers on where I could start? Dan |
|
From: Steven S. <sta...@oc...> - 2008-11-28 08:33:11
|
All, I am very pleased to announce the initial release of JUnit Remote! JUnit Remote provides test remoting for JUnit 4.x test suites. JUnit Remote is primarily targeted at providing in-container testing for Enterprise Java(TM) applications. Remote test invocation is accomplished by dispatching requests to a remote endpoint which executes the tests server-side. Test results are returned using the traditional JUnit 4.x mechanism which allows existing tools and libraries to function without modification. The JUnit Remote project is hosted by SourceForge.net, and may be found at: http://junit-remote.sourceforge.net/ File releases are available at: http://www.sourceforge.net/project/showfiles.php?group_id=245978 Regards, -- Steven Stallion Senior Software Engineer Object Computing, Inc. http://www.ociweb.com |
