QA - BooLAW/Zelda-Project GitHub Wiki
#QA PLAN
###Iteration QA Workflow (Pre-Vertical Slice) During pre-production phase, we are implementing the main framework of the game, thus reating hte base of such. In ordre for it not to crumble when we start implementing the core gameplay changes and additions to the game. Every build release there will be up to 2 days to do the Task Revision, in order to solve the most critical errors and making sure that the main core of the game will work towards the next build. Low priority Issues should better be quarantined and taken towards next revision, unless tehre is enough time to solve them.
###Feature addition Workflow (post Vertical Slice - Pre Beta) After the release of the Vertical Slice, we will only be releasing builds with more content and new features, but not updating the game structure. Thus our focus has to shift towards making the game fun and making sure that there as less technical issues as possible, at least making sure that the game is fully playable with no critical errors. For this the addition of features will always be stopped ideally 2 weeks before the external releases ocurr, leaving time to do external test and receiving feedback and having enough time to fix the issues received. We will always push for at least 1 week of fixing time.
###Beta Workflow (until Gold) At this point the game is fun, feedback is mostly positive and we are able to focus completely on bug fixing. The tests keep on going, but our focus is on finding where some issues come from or discovering new issues that have slipped through our hands during previous phases. The process does not vary much from the previous one, but now we are only focusing on bug fixing. Every iteration should take from 2 to 3 days, an iteration process that will start from the beta release.
