CPSC 480-010 Software Engineering (SE) Fall 2023

The project, Vector Angle, calculates the degree angle between two vectors. It uses the function dotProduct(), of which there is a test program dotProductTest.cpp.

The repository for this assignment is a GitHub Classroom Group Repository. That means there is one repo per team. Have one person create the Team in GitHub Classroom; the rest can join after that.

Your assignment is to add test cases to the file dotProductTest.cpp and get the tests to run successfully.

I assume you are using GitHub Codespaces for the rest of this. If you are not, you must clone the repository locally.

First, build the program:

Then, run the program:

The test program is a separate executable, dotProductTest. To run the test program there is a target, test. So run the test program:

For this assignment, add tests so that when the complete test program is run, all of the code in dotProduct() is run at least once. This would be 100% code coverage.

The workflow is:

• Pull commits so that you are starting with the most recent version of the files.
• Add a test case to dotProductTest.cpp that executes at least one line of code that was not executed using the previous test cases.
• Build the program and deal with any syntax errors.
• Run the test program and see that it passes. If it does not, then your test case is likely incorrect.
• Once the tests all pass, commit the change using the appropriate commit message.
• Push the commit and verify that the new test case shows up at GitHub.

Keep in mind the following:

• Each commit can only add one test
• The commit message must be: "Add test …" where "…" is filled in appropriately. For the first test case already in the test program, the commit was:
• No extra test cases are allowed. Do not add a test case covering the exact same code as another test case.
• Follow exactly the programming style of the first test case. This includes indentation, formatting, use of whitespace and blank lines.

I encourage as many team members to commit a test case as possible based on the machines available. If using GitHub Codespaces, each team member has their own codespace. After a team member has entered a test case, the rest can use a pull to update what they have:

For today, add test cases one at a time to prevent merge issues.

Each team member must submit notes, including for each test case:

• Parameter values used along with the expected answer
• Lines of code each test case individually covers. This would be in the function dotProduct() and does not include empty lines or comment lines.
• The percentage achieved of the total lines by this test case

Each team member's notes are due by the end of the class along with the commits with the test cases. Your score is based on the notes, and on the commits in the team repository.