Guided: Test Driven Development While Building a Set Class - Java 17

In this section, you will implement the contains method for a Set class. This will require making minimal changes to the add method. While doing this, we will follow steps that we would take when building out this feature using Test Driven Development (TDD).

For reference, this process involves small steps to achieve the end goal. We write a test, see it fail, implement basic functionality to get to a green state, and perform refactors as fit. When we perform refactors we go from a green to green state, this means that all of our tests pass when we start and end a refactor.

The files you will be working on throughout this lab is src/test/java/com/pluralsight/SetTest.java and src/main/java/com/pluralsight/Set.java. The objective is to create a functioning Set class that can be used like one would expect a Set object would be. However, we will not be focused on performance like a traditional set.

The solution file for a task that is implementing functionality can be found in soln/step1/{corresponding task}/Set.java.

The solution file for a task that is implementing a test can be found in soln/step5/SetTest.java.

It is important to note that if the task you are working on asks you to implement a test, you will be working in the src/test/java/com/pluralsight/SetTest.java file. Otherwise, you will be implementing functionality in the src/main/java/com/pluralsight/Set.java file.

To run tests, use the command mvn test.

In this section, you will implement the add method for a Set class. While doing this, we will follow steps that we would take when building out this feature using Test Driven Development (TDD).

For reference, this process involves small steps to achieve the end goal. We write a test, see it fail, implement basic functionality to get to a green state, and perform refactors as fit. When we perform refactors we go from a green to green state, this means that all of our tests pass when we start and end a refactor.

The solution file for a task that is implementing functionality can be found in soln/step2/{corresponding task}/Set.java.

The solution file for a task that is implementing a test can be found in soln/ste5/SetTest.java.

It is important to note that if the task you are working on asks you to implement a test, you will be working in the src/test/java/com/pluralsight/SetTest.java file. Otherwise, you will be implementing functionality in the src/main/java/com/pluralsight/Set.java file.

In this section, you will implement the remove method for a Set class. While doing this, we will follow steps that we would take when building out this feature using Test Driven Development (TDD).

For reference, this process involves small steps to achieve the end goal. We write a test, see it fail, implement basic functionality to get to a green state, and perform refactors as fit. When we perform refactors we go from a green to green state, this means that all of our tests pass when we start and end a refactor.

The solution file for a task that is implementing functionality can be found in soln/step3/{corresponding task}/Set.java.

The solution file for a task that is implementing a test can be found in soln/step5/SetTest.java.

It is important to note that if the task you are working on asks you to implement a test, you will be working in the src/test/java/com/pluralsight/SetTest.java file. Otherwise, you will be implementing functionality in the src/main/java/com/pluralsight/Set.java file.

In this section, you will implement the size method for a Set class. While doing this, we will follow steps that we would take when building out this feature using Test Driven Development (TDD).

For reference, this process involves small steps to achieve the end goal. We write a test, see it fail, implement basic functionality to get to a green state, and perform refactors as fit. When we perform refactors we go from a green to green state, this means that all of our tests pass when we start and end a refactor.

The solution file for a task that is implementing functionality can be found in soln/step4/{corresponding task}/Set.java.

The solution file for a task that is implementing a test can be found in soln/step5/SetTest.java.

It is important to note that if the task you are working on asks you to implement a test, you will be working in the src/test/java/com/pluralsight/SetTest.java file. Otherwise, you will be implementing functionality in the src/main/java/com/pluralsight/Set.java file.

In this section, you will implement the clear method for a Set class. While doing this, we will follow steps that we would take when building out this feature using Test Driven Development (TDD).

For reference, this process involves small steps to achieve the end goal. We write a test, see it fail, implement basic functionality to get to a green state, and perform refactors as fit. When we perform refactors we go from a green to green state, this means that all of our tests pass when we start and end a refactor.

The solution file for a task that is implementing functionality can be found in soln/step5/{corresponding task}/Set.java.

The solution file for a task that is implementing a test can be found in soln/step5/SetTest.java.

It is important to note that if the task you are working on asks you to implement a test, you will be working in the src/test/java/com/pluralsight/SetTest.java file. Otherwise, you will be implementing functionality in the src/main/java/com/pluralsight/Set.java file.