Friday, 6 April 2012




  1.  
Name of the Project
Game Engine

  1.  
Objective/ Vision
  1. Test automation  of gaming application poses many challenges. Testing tools should make sure that functionalities are working as expected. The tools should also make sure that there are no regression from new releases of the application. There could be way to create the test scripts either manually or by recording and then a mechanism to run these created scripts. 
  2. Two major components to be implemented.
a)    Create a test script either by recording or manually
b)    Playback (run) the created scripts.
c)     Report the discrepancies via  playback log


  1.  
Users of the System
Any customer who are developing gaming application

  1.  
Functional Requirements
(Atleast Eight)
i.      Come up with different possible testing scenarios for gaming application.
ii.     A recorder for capturing test scripts
iii.    A mechanism to manually create the test script
iv.    Playback engine to run the created scripts.
v.      Data validation (verification points) capabilities.
vi.    Data drive capabilities for running the script against external data source.
vii.   Playback log for reporting discrepancies
viii.  Integrate with browser or Eclipse IDE



  1.  
Non-functional requirements (Atleast Four)
1 ) Secure access of confidential data (user’s details). SSL can be used.
2) 24 X 7 availability
      3) Better component design to get better performance at peak time
      4) Flexible service based architecture will be highly desirable for future extension

  1.  
Optional features


  1.  
User interface priorities
A. Professional look and feel
B. Use of AJAX atleast with all registration forms
C. Browser testing and support for IE, NN, Mozila, and Firefox.
D. Use of Graphical tool like JASPER to show strategic data to admin
E. Reports exportable in .XLS, .PDF or any other desirable format

  1.  
Reports
At the end of the playback of the script, generate a log for each action that was executed

  1.  
Other important issues


  1.  
Team Size
Min 2 to Max 4 team members

  1.  
Technologies to be used
UML, J2EE, XML, e-Forms, AJAX, Web 2.0, Web-services, SOA

  1.  
Tools to be Used
·         ROSE/RSA / WebSphere Modeler
·         Rational Team Concert
·         Rational Quality Manager
·         Eclipse/ RAD / Lotus Forms Designer / Portlet Factory
·         WebSphere Portal/ WAS/ WAS CE / WPS
·         DB2 Express – ‘C’ or DB2 UDB
·         Tivoli CDP/TSM / Tivoli Directory Server
·         Linux will be the preferred OS.

  1.  
Final Deliverable must include
1)     A documentation on how to use the product
2)     Libraries and Source code of the project

No comments: