In this chapter, we reviewed several concerns about the management side of the testing activities. First, we learned that testing can be made in different parts of the software development process (software lifecycle) depending on the test methodology: BDD (acceptance tests are defined before the requirement analysis), TDD (tests are defined before the design of the system), TFD (tests are implemented after the system design), and TLD (tests are implemented after the system implementation).

CI is a process more and more used in software development. It consists on the automated build and test of a codebase. This process is typically triggered with a new commit in a source code repository, such as GitHub, GitLab, or Bitbucket. CI is extended to Continuous Delivery (when releases are made to development environment) and to Continuous Deployment (when deployment to production environment is made continuously). We reviewed two of the most used build servers nowadays: Jenkins (CI as a Service) and Travis (in-premises).

There some other tools that can be used to improve the management of tests, for example, reporting tools (such as Maven Surefire Report or Allure) or defect tracking systems (such as JIRA, Bugzilla, Redmine, MantisBT, and GitHub issues). Automated static analysis is a great complement to testing, for example, using linters such as Checkstyle, FindBugs, PMD, or SonarQube, and also peer review tools such as Collaborator, Crucible, Gerrit, and GitHub pull requests reviews.

To close this book, the final section of this chapter presents a complete web application (named Rate my cat!) and its corresponding JUnit 5 tests (unit, integration, and end-to-end). It consists on a web applications developed and assessed using different technologies presented throughout the book, namely, Spring, Mockito, Selenium, Hamcrest, Travis CI, Codecov, and SonarCloud.