Thanks for your reply. A couple of questions
Since, as far as a web application is concerned, all GUI actions just result in requests, servlet testing can be separated from GUI testing.
Yes this is ok because we do have separate unit tests which tests each servlet. The user interface is not involved at unit test level of the servlets.
My problem is i want to test the actual web pages. Forms, textboxes, listboxes text on the screen and so forth. The tools i mentioned earlier emulate the browser so my testing will not really be valid as i need the data to be sent by the browser that the user will use.
Tools like httpUnit, jwebunit dont actually use the forms but they send the requests to the servlets.
1. Write a filter to capture all details of requests and responses in some sort of general format. Be sure to capture all headers in a usable form. Choose a format for recording requests that will be easy to hand edit to create new scripts.
2. Have multiple users try the application as it is now, recording as above.
3. Write code to use HttpClient or one of the other client emulators to execute "scripts" based on your recorded sessions and your new scripts.
Im new to
Java so ill need a slightly expanded explanation
- What exactly is a filter and how does it capture requests and responses?
- When you say recording do you mean recording the user's actions or the requests?
- Please explain point 3.
Thanks in advance