Know more about Game testing-How and When?

Game Testing Strategy:

Evaluation of game rules:

Game rules adequately explain operation of all components of the game including features, free games etc. Game functions as defined by rules.

UI, Functional, Performance and Compatibility test:

Verify Games outcome and data are correctly shown when games are played. Verify Game Functionality such as Game Progress, game outcomes, handling of incomplete and re-started games, multi player games.

Verification the Integration points:

Check if game win determination aligns with game rules.

Reviewing gaming procedures:

Procedures will be reviewed by System management, player account management, tournaments and promotions.

Infrastructure and security review:

Require to verify all equipment and network implementation. Secure and reliable operation for example time synchronization, OS reliability and security.

How to Test Games?

This process is almost similar to product or web application testing. Here is the typical game testing process:
Identification: First analyze and identify the game rules and behavior
Functional Testing: Ensure game works as intended. This also includes integration testing with third party tools used if any.
OS and Browser compatibility: Most critical game testing part is to ensure game works on required Operating systems. For online games check functionality on all intended browsers.
Performance testing: This becomes critical for online games if gaming site handles betting on game. Game testers must verify if Game Testing site smoothly handles customer load.
Multi player Testing: For multi player games you need to verify the game functionality to handle all players and functionality with fair distribution of game resources to all players.
Reporting: Bug reporting to developers. Bug evidence need to produced and submitted through bug reporting system.
Analysis: Developers hold the responsibility to fix the bugs.

Verification: After the fix, bug need to be verified by the testers to confirm that it shouldn’t reappear.

Game Testing- An interesting area to explore

The video game testing industry is set to become the largest industry. In spite of the recession, there was no dearth in the sales of the game titles, although the game console sales were hit and the game testing companies had to revamp their strategies.

Gaming had its ups and downs over the years but it continues to grow leaps and bounds. Facebook application games are really path breaking with budding developers experimenting their knowledge. Episodic games are the new thing. Games for the iPhone are the new frontier.

So, no one in the game industry knows where games will be even two or three years from now. The only thing they know is that everything is changing and that the games that are released in a few years will be different from what we have now.

Testing video games is equally challenging as game tester needs to have a solid writing skill, very good communication skill and habit to keep attention for details.

Video game testers play critical role in game development industry. As video game programmers spend years deigning video games and video game tester needs to make sure it’s ready for release in very short time span.

What is a typical Game Testing Process?

Computer games take from one to three years to develop (depending on scale). Testing begins late in the development process, sometimes from halfway to 75% into development (it starts so late because, until then, there is little to play or test).

Once the testers get a version, they begin playing the game. Testers must carefully note any errors they uncover. These may range from bugs to art issues to logic errors. Some bugs are easy to document but many are hard to describe and may take several steps to describe so a developer can replicate or find the bug. On a large-scale game with numerous testers, a tester must first determine whether the bug has already been reported before they can log the bugs themselves. Once a bug has been reported as fixed, the tester has to go back and verify that the fix works - and occasionally return to verify that is has not reappeared.

Why do you want to Test the Software?

This is quite a complex question. Testing should be necessary inorder to evaluate the quality of the product. Please note that testing never improves quality. It only evaluates the quality of the software. Testing is the process of questioning a product inorder to evaluate it. As a customer or user, we do not know how the application is going to respond on different inputs supplied by the customer or user. Testing gives an exact information about the behavior of the system. Testing should always be a challenge. 


The exact definition of testing by all means is" Testing is an infinite process of comparing the invisible to the ambiguous so as to avoid the unthinkable happening to the anonymous".

"Always test to break the software".

TESTING QUESTIONS ASKED BY VARIOUS MNC'S- DO ANSWER IT

1) Why do you wish to chose testing as your career?


2) What is the difference between core product testing and end product testing?


3) You have been given an application and asked to test in one day. What would be your approach?


4) What is Integration Testing?


5) What are the white box testing techniques?


6) Write test cases for Yahoo Messenger Login?


7) What are the types of testing?


8) Tell me the greatest bug you have found in your career?


9) What is web testing?


10) What is performance testing? Why do you want to use automation in performance testing?


11) What is Agile testing?


12) Tell me the difference between end- to- end testing and endurance testing?


13) Do you think development is difficult than testing? If So, why?


14) What is Smoke testing? What is the difference between Smoke testing and Sanity testing?


15) What is a Test Plan?


16) What is the difference between Test Plan and Test Strategy?


17) Can you tell me if Manual or Automation is best? Explain with reasons.


18) Explain a critical bug you found in automation?


19)What is Cyclomatic Complexity?


20) Which SDLC models you guys follow in your organization?


21) Why Software needs testing?


22) What is the outcome of testing?


23) How will you choose your Test Team?


24) Give me a list of Functional testing tools?


25) What is Tracebility Matrix? Do you think Traceability Matrix is necessary?


26) How many types of SDLC models do you know?


27) What is peer review? Who shouldn't attend that meeting?


28) What are the methodologies you have used to develop your test cases?


29) What is meant by Impact Analysis?


30) What is Quality Assurance?


31) What is the difference between Quality Assurance and Quality Control?


32) What do you mean by a TEST BED?




Please add your suggestion to improve this.

key Challenges in Software Testing-

This is a very familiar question asked by most of the interviewers.  Most of the challenges faced by testers are:


1) Requirements are not clear.


2) Lack of communication between tester and developer.


3) Lack of testing tools.


4) Lack of training.


5) Bug in software development tools.


6) Miscommunication


7) Lack of testers on bench.


Please do suggest additional points if you have.

TEST PLAN- WHAT IS IT?

Test Plan is a document containing the objective, scope and research of the software project to be tested. This document is prepared inorder for the people outside the test group to understand that how the testers have validated the product. The document includes:


1) Features to be tested.


2) Features not to be tested.


3) Test Strategy.


4) Project Risk Analysis.


5) Test Environment.


6) Entry and Exit Criteria.


7) The way in which the testing has to be done.


8) Testing tools to be used.


9) Software product overview.


10) Scope and limitations of testing.


11) project Deliverables.


12) Testing Priorities and focus.


Please do add if I have missed something. 

*Testing is never an activity but a challenge*

TEST-TO-BREAK THE SOFTWARE.: MAJOR BUGS CAUSED WITHOUT THE TESTERS

TEST-TO-BREAK THE SOFTWARE.: MAJOR BUGS CAUSED WITHOUT THE TESTERS