When a new release is available, regression testing plays an important role in checking that changes do not negatively impact other parts of the software. The length of these tests might however conflict with the goal of having shorter release cycle. In their article, Kim Herzig, Michaela Greiler, Jacek Czerwonka and Brendan Murphy present a strategy that accelerates test processes without sacrificing product quality.
Mockito is a popular and powerful open source Java mocking framework. In order to achieve good unit tests, you need to make use of mocks and stubs. And that’s exactly what this talk will be about: What is a mock?
Testing the graphical user interface (GUI) is one of the most important task of the functional testing phase, as its quality will often greatly influence the customer opinion of your application. In this article, Denis Markovtsev discusses the different types of GUI testing and presents the best practices to automate this activity.
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.
Copyright © 2009-2024 Software Testing Magazine by Martinig & Associates