While 57% of defendants say their teams have either “fully embraced Continuous Testing” or the “vast mainstream of teams are practicing Continuous Testing,” detailed replies surfaced several areas for development.
The survey found that automation was not being used extensively. Only 17% percent of respondents demanded to use automation throughout the testing procedure, and only 22% claimed to have attained in-sprint automation. At this point need to change processes and tools to remove bottlenecks in the software delivery lifecycle.
Until companies match the speed of testing to the speed of development, the quality will endure being a bottleneck to receiving new functionality into the hands of end users. This, in turn, directly impacts an organization’s ability to achieve and maintain a competitive advantage.
Test environments are also clearly causing substantial frustration and delays, with 81% of respondents claiming that their agile teams spend more than 30% of their time getting test environments right. Offering complete test atmosphere on demand, consisting of test data and virtual services, will offer great returns.
Respondents recognized several areas that may positively impact application delivery counting developing and testing against virtual systems, and offering developers to work in parallel. Searching for, managing, and generating test data was identified as an area causing substantial delays. Accepting what is really going on in the process was another important concern.
Almost half of the respondents said that knowledge sharing and identifying bottlenecks are very challenging topics. Survey participants also felt that several other continuous delivery difficulties were impacting their continuous testing process.
- The statement that releases are receiving very difficult, often involving different applications with dependencies and various technologies with potentially conflicting resources
- The goal to standardize and automate the release process
- The need to understand what application comfortable is in what release, and the status of that content in the pipeline
- The capability to report testing handoffs, communications, atmosphere management, promotion, and validation.
The orchestration was seen as an important solution to address these concerns.
What the Future Holds
In the near future, we’ll see test recommendation, orchestration and execution get much more precise and efficient via artificial intelligence (AI) technologies and machine learning. Tools will be acclaimed and run tests based on what is in the pipeline, and alert teams when additional tests are required.
Continuous development (CD) will be built into every application release cycle through ongoing data analysis from the pipeline and production, allowing teams to identify and address problem areas — always focusing on increasing efficiency while decreasing risk.
In the short term, companies are more fictional to add more automation in test data and model-based testing. Respondents said that the most interesting advanced testing techniques include automated test environments and automated test data, which is in line with stated pain points.
The report is based on 500 interviews with senior-level IT executives from large and medium-sized companies (over 1,000 employees) in industries including financial services, high tech, healthcare, and life sciences, telecommunications, media and entertainment, and manufacturing.