I was reading a paper about the differences between software development in general and game development, and the authors made some really good points regarding software testing, however their research was not focused specifically on software testing.
So, I decided to collect further evidence regarding this topic to explore the particularities of software testing in game development.
Therefore, I'd like some opinions about it.
So, if you have any experience in software testing, game development or both, please, consider take 10 minutes off to answer a couple of simple questions about this experience and give your opinion on this matter: https://goo.gl/hrrZEZ.
If your goal is to make your software "as perfect as possible", then there is no difference. You want to test all possible code paths and all "corner" conditions, etc., whether a game or "business" software. You want to make certain that your application (whether a game or a payroll program) validates input data, protects any PII or monetary type data that it may work with , etc. Obviously, if your game is simply a game of chess with no registration or money accounting, etc., you won't be checking those things, but if your game involves "physics" (spaceships travelling near stars/black holes/etc., you will likely want to test for interactions that a payroll system would not). For your game to be successful, you don't want users to be debugging your application for you - especially "early adopters" who will spread likes/dislikes via social media - if you want to gain and keep market share.
If it's a game that you are just going to use yourself, and not distribute/sell, then it may not matter as much - depending upon whether crashes in the middle of the game annoy you or not...
My view is, if you are testing a software, then you have to check the successful achievement of functional and non-functional requirements of the users. IN other word the quality. Then testing is noting but test your requirement satisfaction. Even same two scenarios, say Payroll, the testing may different from each others. Then definitely, its a different in game testing, as the users are very special.
Likewise traditional software, the generic phases of life-cycle in game development are totally covered ( inception, analysis, design, implementation, test, deployment and maintenance). Besides, units test, integration test should also be performed for this kind of development. Meanwhile, the difference could be highlighted at the level of acceptance test. Since customers, who are responsible for expressing the corresponding test cases, are in many times absent, and given that games are public oriented software and not usually tailored for a specific customer.
Guys, those are really good points. These is exacly the kind of discussions that I want to raisde on the research I'm performing.
So, would you guys mind to take some more 10 minutes off to answer the questions in this survey? https://goo.gl/hrrZEZ.
I promise it won't take more than that and I will have the means to add your point of view in the research.
Thank you very much!
Dear Ronnie,
The question form is completed, i hope that will aid you in your research accomplishment.
- Badges
- Science topic
- Similar topics
- Mathematics