Here it is at last: my first Top 100 of Software Testing Blogs. For those who would like to read more on Software Testing and QA, I created a list with 100 of the best - or at least most popular - Software Testing Blogs in the world. This should definitely give you enough reading!
I ordered this list by gathering several metrics of each blog, to be more precise: the Google Pagerank, Alexa Popularity, Technorati Authority, number of comments and number of sites linking to it.(Note: Not all statistics were available for each blog. Where a statistic was missing, the blog in question simply scored 'neutral' for that statistic). You can read the algorythm I used to rank the blogs at noop.nl. Many of the results were gathered automatically using my Pagerank Checking script.
Enjoy the list and please let me know which blogs I forgot!
Edit: Meanwhile some kind people have submitted blogs which I did not take into account when I created this list. They will be included in future updates.
Friday, June 18, 2010
JMeter FAQ on testing web services
Q1: The "response data writer" output file remains empty after running my JMeter test.
Q2: After having changed the input xml file, JMeter seems to send the same old xml file content with its request.
Do you know other solutions or tips and tricks for nasty JMeter problems? Add your comments in the post comment section and help other people having a better JMeter experience
- Verify the location of your input xml file on your "Webservice (SOAP) Request" controller. The location might not be valid.
- Check if the xml content in the soap body of your input file has a valid structure. Validate the xml against its XSD.
- Have a look at the jmeter.log file in the \bin directory of JMeter. Usually JMeter logs an error when it encounters an unexpected exception.
Q2: After having changed the input xml file, JMeter seems to send the same old xml file content with its request.
- Uncheck the "Memory Cache" option on the "Webservice (SOAP) Request" controller. By unchecking this option you make sure that the input xml file is read each time you send the webservice request.
- Make sure you don't overwrite the default settings with the settings on your "Webservice (SOAP) Request". Any connection setting after your "HTTP Request Defaults" gets priority.
- This can happen when you don't check for the server response code. To avoid this, add a response assertion checking the response code and fill in value "200" to check for. Response code 200 means the request succeeded. Next time the server is down, your response assertion checking for the response code will make your test fail.
- Probably you are missing some libraries.
Do you know other solutions or tips and tricks for nasty JMeter problems? Add your comments in the post comment section and help other people having a better JMeter experience
Subscribe to:
Posts (Atom)