Write test cases not only for valid conditions (i.e. for intended functionality) according to requirements but also for invalid conditions. This will cover expected as well unexpected behaviour of application under test.
17
Mar 2015
Mar 2015
Write test cases not only for valid conditions (i.e. for intended functionality) according to requirements but also for invalid conditions. This will cover expected as well unexpected behaviour of application under test.
Mar 2015
Mar 2015
Feb 2015
What cannot be achieved over a string of long-mails can be wrapped-up over a single meeting. This ensures saving time and efforts of all concerned.
Feb 2015
Feb 2015
Feb 2015
Feb 2015
Well this sounds very general, but it is very important to follow in every process of software cycle like requirements gathering, analysis, documentation, designing, coding, testing etc., It is absolutely necessary to do it completely “the very first time itself” so that we can save efforts for better utilization.
Also known as: The simplest thing that could possibly work Keep It Simple, Stupid (KISS) Less is more You Ain’t Gonna Need It (YAGNI)
Feb 2015