J2EE Web application environment testing
We are developing a J2EE Web ecommerce system. The testing environment will have multiple Apache/Tomcat web servers, BEA WebLogic App server (possibly 2) and an Oracle DB server. I need to develop the test cases or scenarios for such kind of testing described below:
- If one of the Web servers is hanging or down, what is the user experience?
- How does the Web server caching function work? Does the user still have his session?
- If one of WebLogic servers is hanging, down or disconnected, what happens to the user?
- If all the WebLogic servers are not available, what happens to the user?
- How about database server is hanging or down?
I doní»t know what category of the testing methodology this testing should go under?
If someone can provide me with more thoroughly and detailed procedures, it will be really appreciated.
Re: J2EE Web application environment testing
On some projects I have seen these test classified as error handling during interface testing. On other projects they were classified as recovery testing.
In addition to testing that the system properly handles down servers (proper error message, rollover to a redundant server, or whatever the requirement is) you can test what happens if the server drops mid-transaction.
Tim Van Tongeren