The world isn’t new to the mobile-first approach. Call it convenience or anything else — people are consuming content on their mobile phones more than their desktops and this will only increase in the near future. According to Statista, at least 50% of global online traffic is driven by mobile users. We were going through Adobe Retail Shopping Insights (2020) and found out that more than 42% of consumers have done their holiday shopping via smartphones.

With the increase in open-source software tools, developers have become more powerful. Open Source refers to an openly distributed code which allows users to inspect, modify and enhance it. It includes a license that allows users to utilize the source code and you can also modify and share under defined terms and conditions.

ThoughtWorks is a global software consulting company that releases an insightful Technology Radar twice a year as a round-up of the current state of technological techniques, platforms, tools, and languages or frameworks. We were pleasantly surprised to see k6 featured in the Tools section of Volume 23, the latest volume of the Technology Radar.

Test automation is here to stay. That’s because good test automation reduces manual effort through repeatable, stable processes, increases ROI on testing, accelerates testing and feedback, and in the long run reduces business expenses.

In recent years, there’s been a shift towards broader adoption of JavaScript test automation frameworks. Today our customers are using Cypress, TestCafe, Puppeteer, and most recently, Playwright. Plus, they are often using these alongside existing Selenium and mobile test automation frameworks. The options for testing have increased, and depending on your unique testing needs, you may be adopting one or many solutions in your organization.

In order to learn how to test your APIs, especially how to load test your APIs, let’s first find out some essential info on APIs and RESTful APIs.

Performance Testing coverage needs to be defined from the application under tests functional requirements and this does not change regardless of whether you are following an Agile or a more Planned approach.

Mobile applications these days have become imperative for businesses. But mobile applications are not just another version of desktop applications. Mobile applications are as much different from desktop applications as mobile devices are different from desktop machines. Mobile applications, therefore, need to be built and tested with this difference in consideration. Following are a few things to consider when testing a mobile application: 1.