cancel
Showing results for 
Search instead for 
Did you mean: 

maven automated "run test case" loses error info

Occasional Contributor

maven automated "run test case" loses error info

Hello,

We are using the maven 2 plugin to run our SOAP U.I. project in an automated fashion.  For normally run test cases, when exceptions get thrown we see a lot of great output such as what was sent in and what exception came back -- the whole xml tree for both request and response.  However, if we are using the "Run a test case" step and an exception gets thrown inside that test case...the response back is murky at best:

"  X test case Failed
  [Response is a SOAP Fault]

  Status: FAILED
  Time Taken: 488
  Size: 0
  Timestamp: Thu Oct 02 10:36:16 EDT 2008
  TestStep: X test case
  Response is a SOAP Fault  "

Any chance there's a way to get the rest of the info to float out of there?  It is making it hard to debug our test cases.  Thank you!
4 REPLIES 4
Super Contributor

Re: maven automated "run test case" loses error info

Hi,

Thanks for reporting this, we'll try to have this fixed for upcoming maven-plugin release..

regards!

/Ole
eviware.com
Occasional Contributor

Re: maven automated "run test case" loses error info

Thanks for the reply, Ole.

Would you be able to contact me when it seems the bug has been fixed?  I can be reached at victor.replogle@ontariosystems.com

Thank you,
  --V
Super Contributor

Re: maven automated "run test case" loses error info

Hi,

sure.. will do!

/Ole
eviware.com
Occasional Contributor

Re: maven automated "run test case" loses error info

Thanks, Ole.

I guess my unstated question is also "is there some other way / place that I could go to personally track the progress without your intervention?"  A notification when it is done would still be great though :-)

I wasn't sure if the visibility was that high (to soap u.i. users) or not -- other than watching for release notes at new version times.  Thanks!
New Here?
Join us and watch the welcome video:
API Testing Mistake #2
APITestingMistake#2