# **Project 1**

# **#unit Testing#**

# *=> Part A

## Goal
=> Pick 5 Method to unit test
=> Build unit Test for Basic CC
=> set up enviroment for Building unit tests

=> My teammates and I had our first group Microsoft team  today. We chose the team leader, key responsibilities, and roles.  Setting up our team surroundings and being comfortable with collaboration technologies are the objectives of this project. To write unit tests for the provided source code, team cooperation will be essential. Start examining the code and creating the unit test environment. To ensure the right environment is set up, practice developing simple tests. Contact the team if problems occur. Check the source code for the methods you want to test.

# *=>Part B

=> I began developing the unit tests that were selected for Part A of the Unit Testing project with my team members. Despite the fact that I haven't yet checked the coverage in IntelliJ, I may be finished creating the unit tests.

=> It was fantastic that after finishing part A of the project, my team and I felt assured about moving on to the next stage. We were able to research and comprehend the Java unit testing and JUnit 5 framework used in the project. We've already held two team meetings, and the third is already being organized! Our team's communication is strong despite the fact that we are all quite busy with other classes, work, and life.

=> I was unsure about how many test cases we needed to write and whether the procedure we are testing has a cyclomatic complexity. then realize that in this situation, I would need to test every outcome and execution path for all possible of the method's possible branches. Two excellent essays about branches and how to ensure their coverage caught my attention as well.
This what i choice
CC 1-2 Test =com.gsd.algorithms.sorting.SelectionSort.Sort(int[])
CC 1-2 Test =com.gsd.algorithms.sorting.QuickSort..Sort(int[])
CC 1-2 Test =com.gsd.algorithms.sorting.InsertionSort.Sort(int[])
CC 3 Test =com.gsd.algorithms.datastructures.binarysearchtree.BinarySearchTree.add(Node,T)
CC 4+ Test =com.gsd.algorithms.sorting.Heapsort.heapsort(int[])

=>Microsoft Teams was used for almost all communication, and a check-in team meeting was held there on 10/10 at 5 p.m. Ismael invested the effort to plan git operations to assist in compiling every code pushed to a staging branch, which has helped give validation for individual work on branches. Everyone can see whether the code successfully compiled and was merged in the GitHub Action tab. It also indicates when unit tests fail.

=>Each team member established their own branches and distinct classes for the tests they selected. Concerning problems developed when two teams tested various techniques in the same class. The names of their test classes ended up being identical. (Need to watch how this develops and how this is resolved.) There was confusion on where to push and merge.