Real Poker Online, a web testing project | TestFort

Case Studies: Online Game

You are here

An online game application

Real Poker Online is a client-server Java web-application for simulation of card games led by groups of players. The application provides a possibility to find friends fond of poker all over the world. Friendly atmosphere of the virtual 3D card-room, outstanding user interface, realistic sound, characters and animation make you feel right in a huge casino.

The application was thoroughly tested by TestFort team in order to meet all the key requirements providing its successful launch on the online game market. In spite of the fact that it was a large-scale and time consuming project, the client's demands were met with a highly effective and creative approach and some terms were fulfilled even more quickly than the client had expected.

Languages and Tools

The application Real Poker Online developed with the help of J2SE 1.4 and J2EE 1.3. It allows playing poker in real time limited, making real and virtual bids. Tournaments are supported. Scalable architecture provides for the distributed deployment on multiple servers. Eclipse IDE, Ant, JUnit, XDoclet, Hibernate JDO, Tapestry Web Application Framework, Hessian RPC, Sun ONE J2EE 1.3 certified application server, Firebird RDBMS and Tomcat are the tools the developers used to create the application.

It enjoys Java Web Start client launching technology supported and tested on Windows, Linux, Solaris, Mac OS X. The application has a secure client-server communications. Real Poker Online contains a powerful web interface for management, user administration, billing, statistic and reports features.

The Art of Testing

Taking into consideration the scale of the testing the initial client's estimation was 8000 man-hours.

However, TestFort testers considerably cut this figure by means of low-cost non-trivial approaches, professional technical expertise and creative way of testing for each specified platform. After a thorough discussion of the requirements, a full-dress analysis was made. As a result, we proposed to use mostly automated testing instead of the manual one: black-box, simulation, functionality, stress, usability and bet-logic testing. Therefore, comprehensive testing of the application took only 2500 man-hours instead of intended 8000.