Developers have a large responsibility on their plate, don’t they? Today, quality is a collective responsibility – while we say testers have a responsibility to look at the application from a big and end user perspective, developers are also in stake today – they cannot merely look at system requirements to code away. While this is a starting point, a good developer does a lot more. He/she looks at the application / module under development holistically from a functionality, performance, security, usability angles amongst others. A responsible developer also has robust unit test cases to ensure the quality of the code he writes. He collaborates with testers to understand the test scenarios, quality of the module, where the application is falling short of, what else can be done, to ensure the chemistry is great both from the relationship he shares with testers as well as the product readiness for release.

Read more »