Software Testing Videos and Tutorials: Load Testing, Unit Testing, Functional Testing, Performance Testing, Agile Testing, DevOps
End-to-end (E2E) testing is one of the more common approaches to testing software, but it is complex, fragile expensive and low quality. As soon as we accept that the best way to test our system is to deploy it all together, with everything else that it interacts with and then try broad-brush interactions with the whole lot, we have lost control.
Selenium WebDriver is a great open source tool, but it is not software a testing library. It is a browser manipulation tool. Still, a good deal of software QA projects are built on pure Selenium. Selenide is a testing library based on Selenium for making stable and readable tests.
Hybrid mobile applications, combining the best of both web and native technologies, are gaining popularity for their cost-effectiveness and faster development cycles. However, testing these applications presents unique challenges, particularly with WebViews.
You built an API in .NET, put it in production, customers are using it, and now you have promises to keep. Promises related to the API contract and behavior. A good test suite will help you keep those promises by protecting against regressions.
QA had thoroughly tested the new release, performed Unit tests, functional tests and yet… we still crashed. The ultimate goal in development is to make sure the application works for the end users in the production env, not just in QA. This is where load testing and Gatling come in.
To continuously deliver IT systems at speed with a focus on business value, DevOps high-performance cross-functional IT delivery teams integrate quality engineering in their way of working. Quality engineering is the new concept in achieving the right quality of IT systems. DevOps teams take joint responsibility to deliver IT systems with business value to their users.
The book Evolutionary architecture talks about how software architecture needs to keep evolving with the changes to business priorities and the tech landscape changes, with fitness functions guiding the evolution. The same concept shall and should be applied to the software testing strategy which is what I coin as Evolutionary testing strategy.
Copyright © 2009-2024 Software Testing Magazine by Martinig & Associates