QA Testing For A Game

Due to the nature of QA testing I have had to sign an NDA and cannot refer to the project by name or describe it in any way that could be recognisable. As a result all I can say about the project itself is that its a game that I play a lot: its a fun game and I have found myself playing when I'm not busy.

This is my second time QA testing for a project and I have been active in playing this game and giving feedback to the developers. My experiences as part of this project has been a positive one. It has taught me a lot about how a game progresses from build to build and how we as developers can use the public to help improve our games. Gathering data from us can help identify important quality of life changes to be made, identify what works or doesn't work for the player base and finally its a good way to sift out bugs or balance out a gameplay loop.

For me it helped me put myself forward in a community and share my opinions and findings with industry professionals. Its also a good place to start building professional business relationships because if you do a good or bad job here it will effect both how this company will view you and your broader reputation. So from a career standpoint its good from making connections and gaining experience in the industry.

I think QA testing is an avenue I will continue to pursue because it forces me to be reflective and analytic about what I'm playing. I also like experiencing what other studios are experimenting with and being part of the process involved in a game getting to the public release.