Description
Welcome!
Welcome to your fourth COMP 1510 lab. In today’s lab we will start writing unit tests.
You will have two hours to work on the lab on Tuesday. On Thursday in lab, I will spend two minutes with
each student in a lightning-round face to face marking meeting. After a short break, we’ll spend some
time reviewing some important topics from the lab and lectures, and finish with our weekly quiz.
Take your time. Read each step. Don’t skip anything. Good luck, and have fun!
1 Grading
Figure 1: This lab is graded out of 5
This lab will be marked out of 5. For full marks this week, you must:
1. (3 points) Correctly implement the coding requirements in this lab.
2. (2 point) Correctly format and comment your code.
2 Project Setup
Please complete the following:
1. For your fourth lab, all files must go into the Lab04 folder.
2. After you complete each task, commit and push your change to version control. In order to earn
full marks, you must commit and push after each function is complete. Your commit message must
be a short message to me that describes what you completed for this commit, i.e., “deconstructed
base_conversion”, or “debugged function_name”, etc.
3. Since I am already a collaborator I will pull your future work automatically.
3 Requirements
The instructions for this week’s lab are short and sweet, like me:
1. Copy your source files from the A1 folder in your assignments project to the Lab04 folder in your
labs project.
1
2. Write a suite of unit tests for each of the seven functions you implemented for A1. If you decomposed
a function into multiple functions, you must write a suite of unit tests for each function. Each suite
of tests must provide complete coverage for the function.
3. As you do this, you may decide to “refactor” your code, i.e., change how you decomposed your
solution for each question, in order to make your functions easier to test. Please go ahead and make
those changes. Programmers do this often.
That’s it! Good luck, and have fun!
2