Quantcast
Channel: [Q&A - FAQ Neotys] Last questions
Viewing all articles
Browse latest Browse all 2283

CI Integration : Results : Error Analysis : How to make it better

$
0
0

Hello,

I am running my NeoLoad performance tests with Jenkins CI using windows batch commands passing all diff args etc
At the end of the test , it produces the html report . fine .

When it is run with command line commands, the test report it produces will only be with the Summary page (which is shown in attachment 'Report ' )

When there are errors during my test, ( they could be either assertion errors or any server timeout, or internal server error or anything),
the above summary isn't actually helping me to know where exactly the error happened or what is the nature of the error etc.

The 'Errors' section (attached 'Error section') gives the count of errors
The 'Pages' section gives the count of error happened against any page, but no details on what is type of error to debug or analyze better
The 'Hot spots' section gives again top 5 error with page and parent...but not on the nature of error.

The nature of error can be seen only if the same result is loaded in to the NeoLoad controller GUI where we have the 'Errors' tab in Result section which gives some more details for analysis. plus NeoLoad web gives these in Events tab...

Am looking for a way to see the same details in the report which i generated with the command line , so it will help me for analyzing the results better from one place, and opening result in GUI controller may not be feasible for everyone as its installed only in a slave configured to jenkins.

... any better approach/options here?

Thanks,


Viewing all articles
Browse latest Browse all 2283

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>