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.
Test automation is an essential practice to manage quality in large software development projects. This article discusses the reasons why incorporating test tools during test design is an absolute necessity for ensuring high-quality software products and successful project outcomes.
BugBug is a cloud-based, low-code test automation tool that is an ideal choice for testers, QA specialists, developers, and product managers in Agile teams to enable E2E testing.
Test cases and acceptance criteria are two important aspects of test management. In this article, Ovidiu Donciu discusses the similarities and differences between test cases and acceptance criteria and suggests that we could merge them.
As a software developer, you understand that testing is an integral part of software development. However, software testing is not just about finding and fixing bugs; it is also about identifying and mitigating risks. Therefore, risk management is an essential part of any software testing process, and having a risk management plan in place is critical during the testing planning phase.
Throw a line of code into many codebases and it is sure to hit one or more testing frameworks. There is no shortage of frameworks for testing, each with their particular spin and set of conventions, but that glut is not always matched by a clear vision of how to structure and use tests cases. A testing framework is a vehicle, but you still need to know how to drive.
Test automation is a must for most large and medium-sized software businesses. However, just automation, even implemented in a project according to all the rules, may not be enough. The company will face several new challenges that slow down the team’s work and negatively affect the release speed. It doesn’t sound very optimistic, does it?
Copyright © 2009-2026 Software Testing Magazine by Martinig & Associates