The starting point for the test design should be the list of requirements. If these requirements have not been formally elicited, at least we need to know the SUT features, which reflects the software needs. From this point, several strategies can be carried out. As usual, there is no unique path to reach our goal, which in the end should be reducing the risks of the project.

This chapter reviewed a process aimed to create effective and efficient tests cases. This process involves the analysis of requirements, definition of a test plan, design of test cases, and finally writing the test cases. We should be aware that, even though software testing is technical task, it involves some important considerations of human psychology. These factors should be known by software engineers and testers in order to follow know best practices and also avoiding common mistakes.

In chapter 7, Testing management, we are going to understand how software testing activities are managed in a living software project. To that, first we review when and how to carry out testing in the common software development processes, such as waterfall, spiral, iterative, spiral, agile, or test-driven development. Then, the server-side infrastructure (such as Jenkins or Travis) aimed to automate the software development process in the context of JUnit 5 is reviewed. Finally, we learn how to keep track of the defects found with the Jupiter tests using the so-called issue tracking systems and test reporting libraries.