An important step in finding employment for all jobs in the game tests you want to become a really great video game tester - the star of the team, or at least co-star. To achieve this level of competition means going beyond what errors - search - to form. How exactly does one discover flaws in the game? Ultimately, the most errors fall into two categories - or design flaws and game play, or coding errors.
Understanding that not merely proof of a video game, but rather, are software testing, will help in finding and fault isolation for transfer to the developers to correct. There are universal principles to the discipline of software testing, and when applied to tests on the game, understanding of these fundamentals will trigger the error count - and his salary. Here are asking employers to hire you, and have all the jobs game testing could possibly want.
Software testing is to find mistakes - the more the merrier, the sooner the better. File errors early and often "is a great philosophy to bring to the table, like the previous errors occur in the development process, the easier and cheaper it is correct. But as with many things, so it is easy in theory, is more difficult in practice - not until all the code is linked together, "integrated" at the end of the final test of the game and the game play is possible. So most of the gaming jobs are advertised in test release cycles alpha and beta - but the closer in the alpha phase begins, the better.
At this stage of the game (pun intended), it really worthwhile to conduct what is called integration testing. Are all major elements of the game will integrate well together? Or is the sound out of sync with the video? ¿Se player sync mouth movements? Sound effects in sync with the action of player? Does the game save to disk, if designed for? Is the game compatible with all operating systems compatible? These are just some of the high-level areas you will want to investigate.
Getting to the heart of the matter, it must design an array that covers all major elements of the game and integration, and then break each of these areas further. As an example, consider the storage issue. What are the different means of purchasing items? Buy, find, looting and trade are the main; do not forget to quest rewards. Once acquired, do not stay in storage to quit the game and then return? Can trade with other players? If you fall, do you stay down? Can you sell items you've found? Done? Negotiated? Stole? As you can see, the possibilities are endless.
Jobs include testing the game in mind these details and possibilities. The strategy for dealing with such a large number of possibilities is building an array of test cases based on how often a given scenario or test case is likely to happen. One and classifies individual test cases and scenarios based on the priority: P0, P1, P2, etc. So, obviously, buying and selling an item and ensure they are kept in storage features are very essential to the game - it would be P0. Being able to sell a quest item he stole from a corpse stolen less - for example, a P1.
These are just some examples of applying the basic principles of software testing computer games. Applying these principles to dramatically exploit its error count, what you stand head and shoulders above their peers typical video game testing. Adopting these principles, and learn the basics of software testing, and the number of testing jobs game that can be contracted by simply going to explode.
0 comments:
Post a Comment