Most research on Agile Testing and QA have requirements on highly automated testing/CI and an Agile or Scrum project-management structure. How can we iterate towards a more Agile testing process, with all the benefits that entails, when some of the common requirements are missing or undesirable in the near-term?
One of the activity of software testing engineer at Google is to build and improve the test infrastructure to help software developers to be more productive. In this blog post, Jochen Wuttke gives a concrete example of this task.
Performing testing in an Agile context require a completely different approach to software testing activities that is often named “Shift Left”. This term emphasize the move of software quality activities to the beginning of the software development life cycle. In this article, Kishan Sundar shares his perspective about the consequences for Scrum teams of shifting left software testing in Agile.
How good are your test cases? Maybe they are good, or maybe you need to add some new ones. How to tell? You can measure things like code coverage to check if some parts of your code were not executed. Still, this does not tell you anything about the quality of your assertions and your software testing results. In the extreme case, a test suite with no assertions might still achieve 100% code coverage, although being of questionable value.
Many modern applications are based on a REST API base software architecture and it is important to apply software testing verification to this code. In his article “REST API Test Automation in Java with Open Source Tools”, Vladimir Belorusets provides a good overview on how to test Java REST API with open source tools.
Automated testing is a key success factor when you develop mobile applications. In the Android ecosystem, the free Android Studio tool provides many useful features for apps developers. In this article, Nikolay Belousov explores how you can use Android Studio for software testing and explains how to retrieve logs.
This presentation will show you why the testing pyramid need to be very wide. You will understand why this is an absolute necessity if all possible paths through the application should be tested. In other words, let me show you why your tests must be very shallow.
Copyright © 2009-2025 Software Testing Magazine by Martinig & Associates