We know that static testing is very effective in catching defects early in software development. Serious bugs, like race conditions which can occur in concurrent software, can't be reliably detected by dynamic testing. Such defects can cause a business major damage when they pop up in production. Despite its effectiveness in early defect detection and ease of use, static testing is not very popular among developers and testers. Meena Muthukumaran discusses reasons why static testing is not commonly used or not used optimally: lack of awareness, lack of time, and myths about cost and effort requirements. Meena explains ways to perform effective static testing—identifying your needs, shortlisting the tools based on your needs, creating awareness and a culture for proactively eliminating defects early in the lifecycle, and encouraging effective usage of static testing. She offers various implementation solutions to suit different development methodologies and ways to measure the benefits realized with static testing.
Meenakshi Muthukumaran
Tata Consultancy Services
Meenakshi Muthukumaran is a test automation strategist and consultant with Assurance Services Unit of Tata Consultancy Services. Meena advises customers on product selection, deployment, and effective use of static testing tools, and leads the professional research team that evaluates and grades different static testing tools. She started her career as a software developer and worked in the United States for several years in technology and management roles. With more than ten years of experience in the IT industry, Meena works with customers across geographies and industries to build high-quality software by addressing their challenges related to code quality and post-production defects.
Speaker Presentations
Wednesday, May 6, 2015 - 3:00pm
Test Techniques
Static Testing: We Know It Works, So Why Don’t We Use It?