Reasons to Consider Software Tests as Products


With DevOps, automated tests have become a crucial necessity. Tests need to be thorough, and their automation should be stable. In fact, tests have to meet quality and robustness criteria that are similar to the application under test, but tests seldom get the attention and investments that the applications get. Where sources and components of applications are considered products that are designed and developed, tests play a mere supporting role. In Scrum projects you will not see tests specified in the backlog. Rather, they are seen as a part of the production for the user stories.

Continue reading “Reasons to Consider Software Tests as Products”


Virtualization—A Tester’s Dream?


Virtualization has been around for a long time. As early as the 1960s, IBM was supporting virtualization on mainframes to ease the cost of migration among multiple generations of their systems. Languages like Pascal, Java, and C# translate into virtual machine languages that are then either interpreted or further compiled (“just in time compilation”) into actual machine code.

Continue reading “Virtualization—A Tester’s Dream?”


How to Improve Test Efficiency with Automation

agile-test-automationAgile’s most defining qualities are speed of delivery and testing friendliness. Automating the tests and building a sustainable, low-maintenance framework is the key to maximizing Agile’s benefits.  Doing it right requires new thinking and strategic methods—not  old or random test automation practices. When coupled with testing and driven by Action Based Testing (ABT), Agile practices will improve system development and test development.

Continue reading “How to Improve Test Efficiency with Automation”


What to Do When Bugs Are Found—Based on When They Are Found

What to Do When Bugs Are Found—Based on When They Are FoundAction Based Testing (ABT) is based on the importance of test design to drive automation success. It uses uses a modular keyword-driven approach, which means that tests are organized in “test modules” and built of sequences of “actions”—each consisting of an action name (keyword) and zero or more arguments. In our TestArchitect tool we define these in a spreadsheet-like format that is easy to work with. Test modules can contain multiple test cases that need to fit into the scope of that particular module. The test cases can form a narrative in which each test case can set up the preconditions for the next one.

Continue reading “What to Do When Bugs Are Found—Based on When They Are Found”