i am to test the performance of web application which includes a small java applet .This java applet is a third party component.It is being embedded to our application.
This Java applet acts as a forex converter.
When we do the performance testing of the web application?What should be the approach? Do we need to test the Javaapplet??or neglect it? any alterantives are welcome? I like to know the approaches for this kind of testing?
OK. let's put forth the hypothesis that you do find a performance problem with the third party component. What is your next step? Do you have access to the code to fix it? If you do have access to the source, do you have the right under your license to change it? Do you have a performance warrant from the vendor to increase performance if a problem is found?
The reason why I bring this up is I find many times that when people test a third party component they have no mechanism to address any performance issue that arises from the test. In essence, all of that time, money and effort was wasted on that component when the effort could have been directed elsewhere.
One strategy you might consider is to test the applet itself to test what kind of throughput you can get through it without the rest of the software stack. A quick test with a few representative function inputs can save project time with developers that want to blame it, and give you a metric you could take to the third party if it were slow.
If you are concerned that embedding the applet might change the performance characteristics, you could ask for a test harness that embeds the applet in the same sort of stack. We do this sometimes with the .Net stack, which also makes it easy to use an http load tool.
This can be reported alongside the results of testing the software in place, but the higher value for your project may be simply in knowing how the applet performs.