If you think that being a game tester is all fun and games, it’s time to think again. Author Jeff Nyman in an experienced game tester, and in this article, his goal is to not only appeal to those who enjoy gaming, but also to provide a certain perspective about testing as a discipline. Nyman begins by sharing an experience he believes all testers should go through and experiment with:
“Being able to spot bugs in games forces you to engage numerous aspects of how your brain takes in and processes information into a cohesive narrative of experience.”
With the rest of his post, Nyman shares examples of the things you have to watch out for during game testing. He then provides a few fun challenges of a game-related nature in which you can pinpoint bugs in browser-based games. Even if you aren’t a game tester, this article provides a number of valuable parallels to testing in general. Take a look!
This past week, software tester and author Eric Jacobson commented on an important bug that happened to escape into production. After the root cause analysis led to a typical response, “If we had more test time, we would have caught it,” Jacobson felt the need to object. After being down this road so many times, he has begun to see things differently. Jacobson asserts that even with more testing time, they probably wouldn’t have caught the bug. Only a rigorous, expensive end-to-end test would have done the trick.
However, Jacobson goes on to suggest a different method that may have proved successful: a mental end-to-end walkthrough without fakes. Attention to “follow-through,” what may happen next per the end state of a test you just performed, could have also been sufficient. For a closer look at Jacobson’s suggested methodology, read on in Part 1 and Part 2 of his article.
Over the last decade, software development and deployment methods have changed considerably with the rising prevalence of Agile approaches. Ensuring application performance has become increasingly important, however, performance testing has had difficulty keeping up with modern testing principles and continuous deployment processes.
It’s true, many organizations still view performance testing as a single experiment, run against a completely assembled, code-frozen environment. But what happens when testers need to validate application performance and reliability before the software is complete, while it’s still being assembled, or when the software will need to be deployed in more than one environment? Check out this video in which Eric Proegler suggests strategies and techniques for testing early and often, while also deconstructing “realism” in performance simulation.
4. Discussion: Where do you find your fun?
Though software testing, at times, may seem like all work and no play, certain aspects can be incredibly rewarding. Whether it’s the exploration and learning through/about the testing process or discovering what a new build is actually like to use, there are a number of areas in which testers find their fun.