Tutorials and resources on how to apply test automation in software testing
We all know that test automation is a must if you hope to perform software testing on a large e-commerce project. However, there is more than one way to write tests for your software, and each has its own pros and cons.
Artificial Intelligence (AI) and Machine Learning technologies are slowly finding a place in many aspects of digital organizations. In this article, Stella Murugesan explains to us what their impact on software testing could be. Automatic test cases creation anyone?
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.
Are your full stack acceptance tests slow, non-deterministic and hard to maintain? You’re not alone. Imagine running hundreds of them in a few seconds, giving the same result every time. How do you think a feedback loop that fast would that affect your team’s productivity?
More and more organizations build test automation frameworks based on the WebDriver and Appium tools to perform software testing their web and mobile projects. A big part of why there are so many flaky tests is that we don’t treat our tests as production code. Moreover, we don’t treat our framework as a product.
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.
Running more than 5000 automated system tests on a deployed application with outgoing connections to about 25 other systems, each with their own dependencies, where test data is complex and needs to be in-sync, is a great challenge. Doing it every night, year after year, with the requirement to fail only on the event of actual errors in the application under test, is a nightmare.