I’m doing an academic project and I’m not asking for help, only suggestions for content when it comes to testing:
Basically I have made a game, and I’ve been advised to AVOID writing about low level testing and just put a brief section dedicated to testing. But what on earth do I include? My game is quite complex so maybe just a test case table for the main functions saying they work correctly? If so, isn’t testing about TRYING to crash the software?
Of course I’ve tested my application frequently as a built it, but there was no real structure. If I’m to fill just a single page or 2 on high level testing, what would people suggest? I have to put something in.
Thanks!
This all depends on the kind of project. If you are writing from a scientific point of view, that is, your program was designed to show the feasibility of some theory or to yield numerical results, a single paragraph about the presence of testing and a table of the tested aspects suffices.
If you are writing from an engineering POV (say, a thesis in an engineering-oriented CS course), you should just write about your methods: How did you select test cases? Did you perform unit testing, system testing or both? Are the tests automated and portable? In short, discuss your approach from a software engineering POV, give a brief overview over what happened, and then show that you learned your trade by discussing the merits, shortcomings and experiences of this process.