Parasoft announced the delivery of a new development testing API; meanwhile, a Typemock survey indicates the need for developers to test their own code.
Parasoft, a maker of software development and testing tools, has announced that the API to its Development Testing platform is now available.
Parasoft's Development Testing
platform features a policy-driven process, and developers can use the API to more rapidly integrate any software development lifecycle (SDLC) tools to further extend the process visibility and control provided by the Parasoft Development Testing platform.
The Parasoft development testing platform integrates static analysis, unit testing, coverage analysis, peer code review, runtime error detection and traceability. And users can expand the platform's capabilities by adding their own internal, open-source or commercial off-the-shelf (COTS) technology via the API, the company said.
"The opportunity to integrate any SDLC tool into this platform gives organizations a single point of control for all activities associated with developing secure, reliable and compliant code," said Wayne Ariola, vice president of strategy for Parasoft, in a statement. "This not only enables a much better understanding of what is being developed and how it is being developed-it also assists organizations to substantially broaden the scope of development policies being monitored to ensure that software is being developed in line with management's expectations."
Meanwhile, in mid-August, Typemock
, a provider of unit testing
solutions, announced that both software developers and QA believe that software developers need to test their own code, according to the results of a survey the company conducted.
Software developers and QA testers are divided over the effectiveness of and necessity for QA teams, with developers wanting to play a bigger role in testing, according to the survey. The survey participants consisted of about 50 percent developers and 50 percent QA testers.
Developer testing is increasingly important as software is released at a faster pace and with higher stakes. This has led to a change as companies embrace Agile, rapid development practices. 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 big support for QA continuing manual testing. And many respondents said 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.
"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.