I would like to get some tips from peer developers about how you go about testing an application you developed, prior to release to QA. Keep in mind, this is a small scale application (requirements are verbal), and so doing formal testing processes wont work, especially, since your boss told you to develop this app quick, push it out the door.
Despite the time restraints, I would like to make sure it is bug free, however, numerous times in the past, I have had the app sent back to me because clicking the “Reset” button, messes up the other controls alignment etc.
I know there are people out there that develop small scale apps fast, and send them out with minimal bugs. How can I achieve that?
I researched this post, but it didnt quite answer my question.
Testing your code before releasing to QA
Unit testing and something like Selenium for simple UI verification might be enough. You’ve given impossible constraints – testing and pushing it out the door conflict. You can only do the amount of testing that doesn’t compromise the speed issue.
Let’s face it – all software has bugs, and the second law of thermodynamics applies. Even code that works perfectly on the day you ship will evolve and need changes, updates, and face lifts as time goes by.