We all know that QAing your game is a big part of giving your game that finished polish. We all approach these in different ways though.
how exactly do you approach your QAing?
Full Version: Quality Assurance
I fix as many bugs as I can find by myself and then release a demo and have the players brute force the rest of them into showing themselves. 
QUOTE (Vanit @ Mar 18 2011, 02:02 AM) 
I fix as many bugs as I can find by myself and then release a demo and have the players brute force the rest of them into showing themselves.
The more players find bugs the more they'll have a bad first impression of your demo. You DO know right?
He speaks the truth. :X
QA typically can be achieved with a number of volunteers known as Beta-Testers, who know it's their sole responsibility to find and report bugs in a very clear fashion. They must test every aspect of the game and try their hardest to break the game and find exploits. It is a VERY tedious and boring job, and takes up a lot of time.
The best way to achieve a good beta-test is to provide Beta-Testing tools in your game. Dungeons: Critical Hit! does a good job of this by giving you an F-9 key that lets you set the variables and switches, lets you teleport to any map, allows you to have any item etc.
As far as I know, Beta-Testing has been the only way to approach QA.
QA typically can be achieved with a number of volunteers known as Beta-Testers, who know it's their sole responsibility to find and report bugs in a very clear fashion. They must test every aspect of the game and try their hardest to break the game and find exploits. It is a VERY tedious and boring job, and takes up a lot of time.
The best way to achieve a good beta-test is to provide Beta-Testing tools in your game. Dungeons: Critical Hit! does a good job of this by giving you an F-9 key that lets you set the variables and switches, lets you teleport to any map, allows you to have any item etc.
As far as I know, Beta-Testing has been the only way to approach QA.
QUOTE (Titanhex @ Mar 18 2011, 12:12 PM)
He speaks the truth. :X
QA typically can be achieved with a number of volunteers known as Beta-Testers, who know it's their sole responsibility to find and report bugs in a very clear fashion. They must test every aspect of the game and try their hardest to break the game and find exploits. It is a VERY tedious and boring job, and takes up a lot of time.
The best way to achieve a good beta-test is to provide Beta-Testing tools in your game. Dungeons: Critical Hit! does a good job of this by giving you an F-9 key that lets you set the variables and switches, lets you teleport to any map, allows you to have any item etc.
As far as I know, Beta-Testing has been the only way to approach QA.
QA typically can be achieved with a number of volunteers known as Beta-Testers, who know it's their sole responsibility to find and report bugs in a very clear fashion. They must test every aspect of the game and try their hardest to break the game and find exploits. It is a VERY tedious and boring job, and takes up a lot of time.
The best way to achieve a good beta-test is to provide Beta-Testing tools in your game. Dungeons: Critical Hit! does a good job of this by giving you an F-9 key that lets you set the variables and switches, lets you teleport to any map, allows you to have any item etc.
As far as I know, Beta-Testing has been the only way to approach QA.
This. I also play through it several times and try to find any errors.
I create a bug log, complete with priority, description and reproduction steps. After a feature is finished, I give it a playthrough and write down every bug on the fly. After the testing, I fix the critical bugs, implement something new and repeat. If I ever get out of the alpha phase, I proceed to fix the minor bugs.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.