The report contains, Vector says, research that highlights what the software development market is thinking about in regards to key trends such as baselining legacy code, continuous integration and change-based testing. As the demand for improved product quality and regulations become more stringent than ever, the company contends that software testing is an industry in the midst of incredible transition.
The Report was designed to capture the thoughts of industry leaders across the embedded software testing industry to discern:
What trends the market is actually embracing
What users are interested in learning more about
What projects the market plans on addressing in the near future
What capabilities are of interest to users
The purpose of the research was to learn about what the embedded software testing industry is focusing on now and what its concerns may be in the near future. Selected highlights from the findings are:
Continuous integration and continuous testing are critical concepts of interest. Other than the overall term of “embedded software test,” respondents of the Vector Software Annual Software Testing Technology Report were most familiar with the terms continuous integration (CI) and continuous testing. This aligns well with the overall industry shift toward increased quality as continuous integration requires isolated code changes to be immediately tested and reported when added to the larger code base.
Some surprising results came in terms of respondents’ familiarity with the term “technical debt.” About 45% responded that they were “very unfamiliar” with the term (which represents latent defects introduced during system architecture, system design, or system development), and its overall weighted average score for familiarity came in at just 2.33 out of 5. A large majority of respondents (nearly 80%) indicated that they were potentially planning to address bug and defect tracking with their next project. This finding is not surprising given the many studies that have shown that the largest component of software cost is often not the original