36 Sirking Street
6356240 Tel-Aviv, il
+972 (54) 7684139
Developers and QA Testers Agree - Software Developers Must Test Their Own Code, Typemock Survey Finds
Still divided regarding role, effectiveness, and necessity of QA teams
Developer testing is increasingly important as software is released quicker and with higher stakes. This has led to a change as companies embrace Agile, rapid development practices to ensure that they can release working software with few defects in minimal time. Almost all survey respondents agreed that developers must test the software they are coding before handing it off to QA. Respondents also noted that QA teams are not effective in finding most bugs, with almost half of the respondents claiming that QA finds 10 percent or less of the critical bugs in development.
When asked what the biggest value of QA is in software development, the majority of respondents said either that QA offers an extra set of eyes or tests user functionality. There was tremendous support for QA continuing manual testing, while arguing that developers need to play a bigger role in automated testing during the development process. Automated developer testing solutions give developers the ability to catch bugs they would otherwise miss and ensure working software - the paradigm of Agile software development.
"Classic waterfall QA testing is increasingly being phased out of software companies," said Eli Lopian, CEO of Typemock. "Modern developers now have the right tools and processes to catch and correct bugs more effectively while in the development phase. Agile testing, with professional testers and developers working together, on the same team, and with developers engaging in quality practices such as unit testing, leads to high quality software being released on time. This recent survey showed that software developers testing their own code is also something that both developers and software quality testers want. "
The use of information published here for personal information and editorial processing is generally free of charge. Please clarify any copyright issues with the stated publisher before further use. In the event of publication, please send a specimen copy to firstname.lastname@example.org.