Systems | Development | Analytics | API | Testing

Learn the fundamentals of DataProvider and how it can be used in TestNG for automated testing. As the volume of applications increases, software testing teams find themselves overburdened with a “combinatorial explosion” of permutations for their test cases. In the early days, we hard-coded our test cases with the most important workflows, and we wrote bespoke automation scripts, each one to handle its own particular use case.

Today, API-driven microservices applications are a source of speed to innovation and competitive advantage – according to SmartBear’s most recent State of Software Quality – API report: However, this modern way of architecting software doesn’t come without challenges. Neglecting to adapt a new approach to service architecture design with a new approach to the underpinnings – API design and testing – can undermine the efforts.

Most people have encountered frustrating software errors. While the Windows "blue screen of death" was a necessary evil in the 1990s, customers have much more choice in today's software-as-a-service market. A single error or broken workflow is often enough for a would-be customer to switch over to a competitor. Of course, many software businesses mitigate these risks through testing and quality assurance.

Rigidity, delayed updates, or slow time-to-market - these problems can turn software testing into a bottleneck to the development pipeline and eventually a hindrance to the company’s overall growth. This is where agile methodology enters the scene, offering a flexible and responsive testing solution. Since its introduction, agile principles and practices have been popularly adopted among development teams who aim for fast, effective delivery and exceptional software experiences.

Learn the best practices and steps for creating a winning mobile testing strategy. To put any idea into a practical action plan, you need a strategy. Same goes for mobile app testing: if you don’t have a strategy, you can’t test your apps effectively or efficiently. In this blog post, we’ll explain the best practices and steps for creating a winning mobile testing strategy.

Learn about our reimagined mobile test automation pyramid for modern DevOps practices. With the mobile market growing explosively and customer expectations increasing just as rapidly, today’s mobile app development and QA teams are under tremendous pressure to deliver constant updates for their apps while providing a continuous and seamless user experience.

If you are reading this, you have likely already identified a high-level need to scale or improve your current approach to testing without the mass hiring of in-house testers, or shifting left to make devs fully responsible for QA. Partnering with a software testing company is a great start, but what if a vendor offers multiple models? How can you define which software testing staffing model is right for you?

When performance testing you need a set of requirements to measure your response times against. When defining these you should do so with your end users or business teams. It is relatively easy to predict volumes, load and users that will use your application as you will no doubt have some data based on your current systems. It is a lot harder to agree on what the response times of your application should be.