The latest News and Information on Software Testing and related technologies.
Although there’s no denying that manual testing will always stay relevant, there’s an increasing demand for automated testing. It brings on many benefits for companies and teams: time efficiency, extensive coverage. But how to best develop an automated testing strategy? In this article, we’ll show you some best practices in all 7 stages of your test automation strategy to maximize your experiences.
Companies use their data to accelerate business growth and overtake their competitors. To achieve this, they invest a lot in their ETL (extract-transform-load) operations, which take raw data and transform it into actionable information. It’s no wonder, then, that ETL testing is a crucial part of a well-functioning ETL process, since the ETL process generates mission-critical data.
A common complaint that I hear is: “My tests run a lot faster locally than on Sauce Labs.” Sauce Labs is in the cloud and not in your local network, so it makes sense that any given test is going to have some amount of slowdown. The advantage of Sauce Labs is that you can make up this difference by scaling up the number of tests you run at the same time.
“JMeter is old technology”, I hear this a lot. “Let’s use this tool or that tool instead of JMeter as it’s the latest”, I hear this a lot. “We need a lightweight tool without the GUI interface to write our tests as that will make us more agile”, I hear this a lot.
This year the Selenium Conference was held virtually, and despite that, the conference again offered an exciting place for the Selenium community to meet in order to share and learn about the most popular browser automation tool in the world. The conference offered talks about improved testing practices, new tools to simplify the setup of automated tests, the future of Selenium, and lots of learnings from speakers who shared their use cases and practical advice for how they use Selenium at work.
Often software developers get to ask themselves the question: Should I just run the tests in the GUI now that I finished developing them? The answer is pretty simple, NO. You should not use the GUI when running the tests. The GUI should be used only for developing the tests.
