Hot answers tagged standards
I'm going to start with the flippant answers before I give you the real ones. The flip answers are no less correct, they're just not something you're likely to want to hear. There is no standard because it's a meaningless metric. There is no standard because it's a meaningless metric. There is no standard because it's a meaningless metric. Now for the ...
Let them meet (or do an online call) and do a handover: Explain internals Installation documentation Build documentation Deploy documentation The most important thing is that it should be complete and the new developer should be able to build it without to much hassle. Also I suggest you place the actual code in some sort of version control systems if ...
From application perspective you need to look at below states for DB to be validated with basic cases Clean up Scripts (Clearing Previous Run Data) Initial Data population (From a fresh install whatever initial configuration you need to do) Prerequisites Validations Tests (Checklist to validate before you start run - Services up / DB's accessible, able to ...
I think that it is important to understand the difference between testing and QA. There is one post you need to read on the topic by Michael Bolton, Testers get out of the QA business. The short version is that testers, who don't change code, are assisting with quality, not assuring it.
Only top voted, non community-wiki answers of a minimum length are eligible