Webinar Recap: Top Software Testing Trends in 2019
On January 22, Katalon partnered with ToolsQA to discuss the future trends in software testing in the webinar “Software Testing Trends 2019—Stay Ahead of the Game.” We were honored to welcome more than 500 attendees all across the globe.
The webinar was hosted by Mush Honda—Katalon, Inc. advisor and KMS Technology Inc. VP of Testing Services, and Virender Singh—Technology Head and Co-founder at ToolsQA. Honda and Singh took turns to discuss the primary trends of testing activities in 2019 and how to leverage Katalon Studio to stay agile with the trends.
The main goal of software testing is to achieve the Continuous Delivery of quality products, according to Honda.
“Automate essentially everything,” Honda said. “When I say everything, it’s not just testing, but the process of building the application, the ability to create the infrastructure, the ability to deploy it.”
Honda predicted five trends that would shape the industry in 2019.
2019 Top Software Testing Trends
Shift-Left is the practice of testers working more with developers and product owners to test as early as possible. Honda believes that “Automation tools should be added to the developer’s toolkit to enable us as testers [to] integrate much [more] tightly with the development team.”
What this means for testers is that they have to encourage and foster the culture of their own team so as to synchronize and harmonize the way testers collaborate.
Containers and Environment Orchestration
Container technology—found by DZone to be used by 42% of developers—allows teams to no longer have to rely on people in the operations team to run a real environment for them.
Honda said that using tools such as Docker and Kubernetes to create containers and engage in environment orchestration would “help the testers be more independent and be able to create infrastructure on demand,” saving a lot of time.
“From a process perspective, what I recommend as members adopt [container technology] is the creation of consistent test data,” Honda said. “One of the things that containers help you do a lot with is the effective management of test data that you could use as part of your testing.”
Container technology can also help testers and developers access log specific environments and generally address deployment and scaling needs. Honda predicts that just as container technology is being embraced by developers, it will soon be adopted by testers as well due to its advantages.
Better Test Coverage and Test Run Analytics with AI/ML Investment
More new testing tools are using artificial intelligence and machine learning to improve their capabilities. The predictive power of these machines helps testers locate potential problems in the code.
“We need to always look at evolving our testing strategy to start leveraging these predictive analytics,” Honda said. “Insights that AI would be able to generate for us would essentially allow us to point out any gaps that may exist in our preconceived test coverage.”
Honda does not believe AI will replace all human testers, merely that it will help human testers be more efficient and deliver higher quality work.
Exploratory Testing in Production
This type of testing gives testers more control over how to achieve user stories faster and more efficient than regular testing ideal for Continuous Delivery.
“Exploratory testing will focus on allowing our testers to bring more value and focus on business assurance type tests,” said Honda. “The one key thing we have to make sure we do is [that] we expand our testing strategies to allow business assurance in pre-production and production.”
Accelerated Need for Automated Testing of APIs
The growing importance of APIs has dramatically increased the demand for API Testing.
“Not only have APIs become a necessity for application customers to streamline operations right across their entire business and product suites,” said Honda. “They have also become an integral part of product development and business strategy.”
Distributed Architecture and API Testing
Virender Singh then described how the increasing importance of APIs has led to more systems moving toward distributed architecture, where complex programs are divided into specialized components or services.
Singh described the advantages of this model. Each component is responsible for just one task reduces complexity. The components can have different programming language and still interact using HTTP.
Because of the independence of each component and their focus, the load on each individual component is reduced. These components communicate with external entities via APIs. API Testing is faster than UI testing because it does not have to wait for the UI to load. Due to the fact that it talks in pure data, it is more realizable.
Singh then gave a detailed demonstration on Katalon Studio of how to test APIs. He showed how Katalon Studio’s two different interfaces made it ideal for API testing.
With Katalon Studio, users can either write the boilerplate code if they are technically minded, or the interface can do the work if they need help writing tests. Singh praised this feature and Katalon Studio in general as a great tool for API testing.
To start applying API automated testing, download Katalon Studio for free.Trigger modal