Few days back, I read an excellent article by “Dr. Vladimir Belorusets” about how to improve test coverage and avoiding missing test scenarios, He mentioned quite useful points in this article in order to improve communication between Development and QA by establishing the process of accompanying each build with the Build Notes that briefly describe the changes introduced. The following sections in the Build Notes can be added: 1. Changes in functionality 2. Changes in GUI 3. Code refactoring 4. Tests recommended by developers 5. Defects fixed Here code refactoring means changing source code without modifying its functional behavior in order to improve code design and maintainability. As a result, regression testing is required since the developer can accidentally break the functionality that worked before. In the same way, any ‘Changes in GUI’ may impact the existing GUI test automation scripts that are heavily dependent on GUI objects and their properties.
I have been in software industry for almost 8 years, I got the opportunity of developing web/desktop applications in start of my career mainly based on Microsoft framework,I have also worked in Enterprise Business applications in Micrsoft biztalk server , I have keen interest in the field of Software quality and automation.I enjoy Session based testing/Explorator testing a lot.
I believe that software quality is one of the integral part of the software development, that demands good coding practices, timely reviews and verification right from the beginning. One can not 'paint' quality over the product after its development.