A GUI as we now know is a computer-interface that uses images, typed text, and icons on the screen that replace many of the functions of the keyboard. This paper explains different validations need to be used while testing GUI.

Russell Pannone was asked, "Does quality assurance have a place in agile software development?" His knee-jerk answer was yes, but what form and function quality management takes depends on many factors.

Code coverage is an important measurement in software quality engineering. While software testing ensures correctness of the applications, a metric is required to track the completeness and effectiveness of the testing undertaken. Code coverage helps achieve reliable quality through identifying untested areas of the application. It is still a challenge to identify the right code coverage tooling solution. The next challenge lies in formulating the strategy for deployment of the tool and the process. This paper discusses code coverage tooling solutions and deployment strategy for quick benefits.

Most professionals in the software development industry recognize the need for Configuration Management (CM).  CM has been around long enough for people to have experienced problems when CM was either not in place or when the level of CM was insufficient for the needs of the work.  CM values of identification, control, audit, and report are meant to ensure integrity of the product under development.  These days, almost everyone has, at least, version control practices which include a version control tool and a simple checkout/checkin process.  However, as with any engineering discipline, the level of the CM implementation (since CM is much more than just version control) will depend greatly on the culture along with the methods and governance that exist within the company.