C C C Testing Automation of Gaming Application: CCC C C CC CC CC
C C C Testing Automation of Gaming Application: CCC C C CC CC CC
Functional Requirements: 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
More Added: Transaction correction-If something goes wrong, then the stakeholder should be able to change the information as per his authentication provided.
1. Proper Authentication-The system should be provided with better authentication as per the level.
2. The system should also support for forwarding the log to the Developers of the game application.
Non-Functional Requirements: 1. Secure access of confidential data (users 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
More added: 1. Performance- The system should provide the expected throughput and performance. 2. Scalability- It should be possible to scale as per the requirements. 3. Availability As Described above it should be always available (24 X 7). 4. Reliability- The system should be reliable to be trusted. 5. Recoverability- The feature should be there to recover if any loss of data. 6. Maintainability- It should be easily managed.
System:
System is an automated game testing, we have to design script which tests the game and log the errors and the logs are forwarded to the developer for debugging. This system makes most use of the testing tools like eclipse, RAD etc. the game tester is having authentication with use of username and password. More security measures are taken to make the system secure. Playback (run) the created scripts which create
appropriate script for particular game application. Report the discrepancies via playback log and hence used in tracing the errors that are resolved.
Sub-Systems:
Access Security 1. A strict security procedure is enforced so that only authorized users are allowed to gain access to the Gaming Application or Tools for Testing. 2. A unique username and password is provided to each Test script user to log into the system. Within the system, access to the different functions is controlled through the user identification and/or password. 3. This allows full data security linked to the username/password which limits the Tester only to specific functions and processes according to the users privileges. Like just testing without editing any of the test Script.
4. It also restricts unauthorized users to gain access to modules which they are prevented from entering and updating. Hardware System 1. The hardware System is a sub-system of the Game automation testing System that defines required hardware configuration for game testing. 2. Processor required must be compatible with the desired game which is to be tested with the script. 3. As per the game requirement of graphic card if applicable is to be used. 4. Sufficient amount of RAM is required for script to be executed. 5. Network compatible games must have required Network connectivity. Software System 1. Genuine Editors for Writing scripts which parse the gaming application. 2. Compatible operating system on which the game is to be run. (Linux will be Preferred OS) 3. Required UML software for Studying the Application. 4. Required testing tools like Eclipse, RAD etc. Log Maintenance System 1. Error logs of the tested game code must be appropriately maintained. 2. Logs should be accessible to the tester or the Admin of the Game Application. This is important as the entire tested log must not be visible to all the users of the system but to the proper login person who have tested the game. 3. Logs must be forwarded to the game Developer for further Debugging and removing the errors. This provides the error removal and hence makes the game application error free. 4. Log backup must be taken from time to time for the documentation for the errors to be traced. This is important for keeping track of what errors are debugged and that must not be repeated.