The main goal of this course is to familiarize participants with JUnit and the concept of software testing. Upon completion of the course, participants will be able to write effective unit tests in Java using JUnit. They will understand why testing is an integral part of the Software Development Life Cycle (SDLC) and will be familiar with test-driven development (TDD) and behaviour-driven development (BDD).

This course is aimed at introductory level participants, including newcomers to software development and testing. It is suitable for both programmers with no previous testing experience and testers who want to expand their skills into JUnit and test automation.

No specific prior knowledge is required to participate in this course. However, a basic knowledge of programming in any programming language is considered a plus, as some understanding of code will make sense when writing tests.

The course is offered through instructor-led lessons as well as self-study. Participants will receive practical exercises and assignments to practice their skills. The emphasis is on hands-on learning, where participants are actively writing code and solving programming issues.

Software testing

o Framing the role of testing in the SDLC

o Introduction to terminology (test cases, test scenarios, BVA, etc.)

o Know test levels and explain their roles (unit, integration, system and acceptance)

o Test automation and its advantages and disadvantages compared to manual testing

o Explain TDD (test-driven development) and BDD (behaviour-driven development)

• Testing in Java

o Loading the appropriate version of the JUnit framework via a project management system

(e.g. Maven, Gradle, etc.)

o Understanding the package structure, test code and source code according to the conventions of the

JUnit framework

o Application of the various annotations and methods to, in an efficient way

and, in accordance with best practices, to carefully and thoroughly test your own source code (unit tests)

o Performing tests via both the IDE integration and in the terminal (via the build tool)

(e.g. Maven)) and obtaining test coverage in percentage

‍