NeoLoad

http://www.neotys.com/product/demo-neoload.html

http://en.wikipedia.org/wiki/NeoLoad

http://www.neotys.com/load-testing/how-it-works.html

http://bharath-marrivada.blogspot.com/2010/08/neoload-vs-loadrunner-ajax-click-script.html    (Go one to refer for diference b/w NeoLoad vs Load Runner)

Quick Test Pro10.0

http://www.qtp10.com/2009/06/create-qtp-test-scripts-qtp-tutorial-1.html

RIATest tool

The big picture is: QTP - sophisticated, expensive, can automate almost anything, not just Flex applications, works on Windows. RIATest - simple, inexpensive, designed specifically and only for Flex application, works on Windows and Mac. RIATest is a GUI test automation tool for Adobe Flex applications. RIATest is built on top of Flex automation framework and supports Flex 2, Flex 3, Flex 4 and AIR applications. Features Action Recorder to record user actions with Application Under Test and creates test scripts. Component Inspector to inspect and identify application's GUI elements. ActionScript-like RIAScript scripting language to write test scripts. RIAScript is based on ECMAScript. Built-in script debugger with breakpoints, stepping and variable value tooltips. Command line test execution support. http://hubpages.com/hub/Automating-Flex-Applications-with-QTP  http://www.gorillalogic.com/flexmonkium

Web Service Testing

http://www.learnqtp.com/web-services-and-qtp-part-1-testing-web-services-key-concepts/

http://msdn.microsoft.com/en-us/magazine/cc163830.aspx 

http://www.codeproject.com/KB/webservices/webservicestesting.aspx  (Explained clearly regarding web service testing)


Difference between Web application and web service?
A web application is a database disc.
A web service is a online service, as in verizon online service,
               Or a web site service that you went to own or rent.

Web application:

================
any application which resides on a server, but meant for use by humans,
which uses web pages as the presentation layer. All user interactivity (the GUI) is done
through web pages, but all data is stored and (mostly) manipulated on the server.

Web service:

===========
server-based application (as above) which may be accessed over the web via HTTP, but is
meant primarily for interaction with other programs. Thus, it will have a clearly-defined API
which consists of providing responses to HTTP GET and POST requests made by a remote application.
Now, this doesn't mean you can't access a web service from your browser, but it means that the
application won't necessarily have a GUI user interface. You will most likely, for example,
receive all results of GET and POST requests as strings of XML, which requires a client-side parser.

So, think of web applications as completed user interfaces, while web services are more intended to
be application components or "libraries" which can be used by other applications. Essentially,
web services are to distributed applications what DLLs or class libraries are to most traditional
compiled applications.

Also, this means that a web service has to have a more organized design that most web applications,
because there won't necessarily be a human at the other end who can figure out through trial and
error what the app does. This is why the whole concept of "web services" has brought a whole new
set of acronyms such as SOAP, UDDI, etc...