CODEWITHSUNDEEP
javajakarta-eeweb-applicationsautomation
AngelsandDemons
AngelsandDemons

Reputation: 2853

Automating complete testing of Java EE web application

I have a doubt. Say I have a web application which is big and relies on Java/Java EE (JSP/Servlets).

Every time before a drop we test each and every functionality on GUI so that everything is working properly. Previously it was easy but now as the number of modules has increased exponentially, manually testing each and every GUI with required functionality is no more a feasible option.

I am on lookout for tools in which I can write my entire test case say about 1000 and then just run it once before the drop and it will list down all the test cases that have failed.

The tool preferably must be free to download and use it.

I dont know whether using

Arquilian

or

JUnit

in this regard will help or not but automating testing before the drop is really needed.. Please guide.

Upvotes: 3

Views: 2327

Answers (2)

Gab
Gab

Reputation: 8332

Definitively Selenium.
Couple it with maven cause you will probably need to package your project specifically for testing purpose. Moreover maven allow you to launch a container during the integration-test phase and to close it automatically at the end. You can also configure this as a nightly build on jenkins / hudson so you will be quicly notified of any regression.

Upvotes: 1

urbiwanus
urbiwanus

Reputation: 733

Use Junit together with a mock framework i.e Mockito to test units (service methods)

Use Arquillian to test on an integration level ( how different services, modules work together )

Use a database testing tool (i.e dbunit) to test your database / persistence layer)

Use Selenium to test your frontend

Test as much as possible.

Use Jenkins and Sonar to track your build process and your quality of tests and code

You should always test your application on different level. There is not just one solution. Use unit testing to test small pieces of your application and to make refactoring as easy as possible.

Use integration test to check your modules still work together as expected.

Use GUI testing to check if your customers can work with your software.

If its relevant, think about performance testing (i.e. jmeter )

Upvotes: 3

Related Questions