A few years ago, it was just considered an offshoot aspect related to the overall development process of software - may that be a mobile app, web/desktop software or a...
Besides finding bugs and other issues with games, a tester also provides the key information to stakeholders through information artifacts. It is an important process where the results are presented in the form of test reports, verbal accounts or bug reports. In order to achieve the maximum accuracy and output from these artifacts, a tester needs to keep a few things in mind. A comprehensive information artifact should have some common traits, which can be mutually beneficial for both testers and stakeholders and should yield the maximum output.
Important attributes of an information artifact:
An information artifact should have accurate and valuable information, which should be complemented by every vital detail. At the same time, this information should be easily understandable and presented in the right format to avoid any sort of confusion. In the end, the most important thing is that the methods and means detailed in the artifact to iron out a bug should be cost effective, which make game testing services viable and implementable.
The process begins by finding the right information, which ultimately makes an artifact valuable. Any sort of trivial information should not be filled in the bug repository, as it would waste a lot of time and would not yield any results.
The bedrock of any information artifact is accuracy. Thus, stakeholders should get all the accurate information from these artifacts including events, environments, outcomes and states among other factors. Any sort of uncertainty in detailing will cause a lot of harm in the overall process of testing. The information provided in these artifacts should be easily understandable. So, they should be written with use the right/proper language, abbreviations and terminology. The stakeholders should understand all the provided information in these artifacts and make complete use of information of the information mined.
Formatting and Cost:
It does happen many a time that stakeholders get multiple information artifacts regarding the same bugs or test reports. To make the process of information filtration easy for them, these artifacts should come in specific formats so that they can be used properly. Besides offering the right information, these artifacts would also save a lot of additional handling cost.
Prior to dispersing the information, tester and stakeholders should agree upon a format for future exchange of information. An information artifact has to be valuable, accurate and should come with understandable information, but ultimately it has to be bound by cost effective steps/measures. Much of all depends upon the testers engaged in the process. Actually, stakeholders cannot deduce the expected cost of these artifacts. At best regular stakeholders of a game title would want all the important information at one place to effect a deduction. But it’s the tester whose role is defined by the effort to find irregularities and facilitate the list of artifacts.
Thus, it becomes imperative for the testers to take the responsibility to make it a cost effective endeavor and let the artifacts comprise of only the important information to save the money and time of the entire game development and delivery process.
Laxmikant B. Thipse
Founder & CEO
GameCloud Technologies Pvt Ltd