14.7. Studio: Unit Testing

LaunchCode's Marketing Team needs your help! To make the website more maintainable, they thought an object called launchcode that contains important facts and functions they need would be helpful. This way if they need to make a change to one of the facts, they just have to change the object in one place as opposed to going through pages of code to make the change in every place.

Here is what they need the launchcode object to contain:

  1. A key called organization with a value of "nonprofit".

  2. A key called executiveDirector with a value of "Jeff".

  3. A key called percentageCoolEmployees with a value of 100.

  4. A key called programsOffered with a value of ["LC101", "LaunchCode Women+", "CodeCamp"].

  5. And a method called launchOutput(). This method will return a string.

Let's use Test-Driven Development to write this code! Rather than complete the code and then test it, TDD flips the process:

  1. Write a test first - one that checks the program for a specific outcome.

  2. Run the test to make sure it fails.

  3. Write a code snippet that passes the test.

  4. Repeat steps 1 - 3 for the remaining features of the program.

  5. Examine the code and test scripts, and refactor them to increase efficiency. Remember the DRY idea (Don't Repeat Yourself).

14.7.1. Source Code

Open this repl and note the files:

  1. index.js holds the object we want to design.

  2. launchcode.spec.js holds the testing script.

The files are mostly empty. Only a framework has been provided for you.

14.7.2. Start With the Properties

Let's start our work with the properties we need to add to the object.

14.7.2.1. organization

  1. Inside the describe function in launchcode.spec.js, write a test that will check that the value of organization is "nonprofit". Run your test.

  2. With your test complete, turn your attention to launchcode.js and add the organization property to launchcode.

  3. Run your tests to make sure that everything works as expected.

14.7.2.2. executiveDirector

  1. Write a new test that will check that the value of executiveDirector is "Jeff". Run your test.

  2. Add the executiveDirector property to launchcode.

  3. Run your tests!

14.7.2.3. percentageCoolEmployees

  1. Write another test that will check that the value of percentageCoolEmployees. Run your test.

  2. Add percentageCoolEmployees to launchcode.

  3. Run your tests!

14.7.2.4. programsOffered

  1. Write a fourth test that will check the value of programsOffered. You should have four expect statements within your test. Three of them should check that the array contains the appropriate values and the final one should check that the array is the appropriate size. Before moving on, take a moment either individually or with a classmate, to reflect on why you would need these four expect statements. Run your test.

  2. Add the programsOffered property to launchcode.

  3. Run your tests!

You now have the properties set up for the launchcode object. Time to move on to creating the launchOutput() method.

14.7.3. launchOutput()

launchOutput() needs to meet the following conditions:

  1. When passed a number that is ONLY divisible by 2, return 'Launch!'

  2. When passed a number that is ONLY divisible by 3, return 'Code!'

  3. When passed a number that is ONLY divisible by 5, return 'Rocks!'

  4. When passed a number that is divisible by 2 AND 3, return 'LaunchCode!'

  5. When passed a number that is divisible by 3 AND 5, return 'Code Rocks!'

  6. When passed a number that is divisible by 2 AND 5, return 'Launch Rocks!'

  7. When passed a number that is divisible by 2, 3, AND 5, return 'LaunchCode Rocks!'

  8. When passed a number that is NOT divisible by 2, 3, or 5, return 'Rutabagas! That doesn't work.'

To make sure that you meet all of these conditions, you need to take it one test at a time.

14.7.3.1. Write the First Test

In launchcode.spec.js, complete the describe function by adding a test for condition #1:

When passed a number that is ONLY divisible by 2, launchOutput() returns 'Launch!'

Run the test. It should fail because there is no code inside launchOutput() yet!

14.7.3.2. Write Code to Pass the First Test

In launchCodeRocks.js, use an if statement inside the launchOutput() function to check if the parameter is evenly divisible by 2, and then return an output. (Hint: modulus).

Run the test script again to see if your code passes. If not, modify launchOutput() until it does.

14.7.3.3. Write the Next Two Tests

In launchCodeRocks.spec.js, add tests for the conditions:

  1. When passed a number that is ONLY divisible by 3, launchOutput() returns 'Code!'

  2. When passed a number that is ONLY divisible by 5, launchOutput() returns 'Rocks!'

Run the tests. The two new ones should fail, but the first should still pass. Modify the it statements as needed if you see a different result.

14.7.3.4. Write Code to Pass the New Tests

Add more code inside launchOutput() to check if the parameter is evenly divisible by 2, 3, or 5, and then return an output based on the result.

Run the test script again to see if your code passes all three tests. If not, modify launchOutput() until it does.

14.7.3.5. Hmmm, Tricky

In launchCodeRocks.spec.js, add a test for the condition:

When passed a number that is divisible by 2 AND 3, launchOutput() returns 'LaunchCode!' (not 'Launch!Code!').

Run the tests. Only the new one should fail.

Modify launchOutput() until the function passes all four of the tests.

14.7.3.6. More Tests and Code Snippets

Continue adding ONE test at a time for the remaining conditions. After you add EACH new test, run the script to make sure it FAILS, while the previous tests still pass.

Modify launchOutput() until the function passes the new test and all of the old ones.

Presto! By starting with the testing script, you constructed launchOutput() one segment at a time. The result is complete, valid code that has already been checked for accuracy.

14.7.4. New Condition

Now that your function passes all 8 tests, let's change one of the conditions. For the case where a number is divisible by both 2 and 5, instead of returning 'Launch Rocks!', we want the function to return 'Launch Rocks! (CRASH!!!!)'.

Modify the testing and function code to deal with this new condition.

14.7.5. Bonus Missions

14.7.5.1. DRYing the Code

Examine launchOutput() and the describe functions. Notice that there is quite a bit of repetition in the code.

Try adding arrays, objects, and/or loops to refactor the code into a more efficient structure.