Your Internet of Things (IoT) solution is unique and you will quickly realize that testing end-to-end IoT performance is hard. This article explains what you should require in an IoT performance testing tool to solve these problems.
The first part of this article presented some of the current challenges of performance testing. It discussed also the data and times pillar of performance testing. This second part covers the resource and cost aspects. The author shares some final thoughts on the future of performance testing.
Agile, DevOps, Continuous Delivery, Testing in Production: all these modern trends put pressure on the traditional approach to software testing in general and more specifically on the performance testing activity. In this article, V.M.Guruprasath explains issues created by the new context and proposes some possible solutions.
It doesn’t matter if you are developing software with Java, .NET, PHP or another language. If you need to do performance testing – it will be a challenging task, especially nowadays with microservices architectures, clusters and very complex systems. This presentation addresses the most common pitfalls of performance tests. The presenter shares his experience gained through demanding experiments and quite often frustrating failures.
Users care as much about how your service performs as they do what job it helps them accomplish. This is why performance is imperative and performance testing a must. So why do we still see so many 503 errors and slow apps? The answer is empathy, a lack thereof. Performance is the most tangible element of “non-functional” quality criteria we regularly ignore until it’s too late.
You are the Selenium master and automate tests in your sleep. You make sure the quality of your companies web page is 100%. But then the team wants you to measure the performance of your site. How do you do that? Is that even possible to measure web performance with Selenium?