Why Code coverage basics in Node.js? - Purpose & Use Cases

The Big Idea

What if you could instantly see which parts of your code are truly tested and which are hiding bugs?

The Scenario

Imagine you wrote a lot of code for your Node.js app, but you don't know which parts actually run when you test it.

You try to guess if your tests cover everything, but it's like trying to find missing puzzle pieces in the dark.

The Problem

Manually checking which code runs during tests is slow and unreliable.

You might miss bugs hidden in untested parts, causing your app to break unexpectedly.

It's like proofreading a book without a spellchecker—easy to overlook mistakes.

The Solution

Code coverage tools automatically track which lines of your code run during tests.

They show you exactly what is tested and what is not, so you can improve your tests confidently.

Before vs After

✗ Before

Run tests and guess if all code paths are covered

✓ After

Use a coverage tool like nyc to see detailed coverage reports

What It Enables

It lets you write better tests by clearly showing which parts of your code need more attention.

Real Life Example

When building a login feature, code coverage helps ensure you test all cases: correct password, wrong password, empty input, and so on.

Key Takeaways

Manual test checking is slow and error-prone.

Code coverage tools track which code runs during tests automatically.

This helps you write stronger, more reliable tests.

Practice

1. What does code coverage measure in a Node.js project?

easy

A. How much of the code is executed by tests

B. The speed of the Node.js server

C. The number of users accessing the app

D. The size of the project files

Solution

1. Step 1: Understand the purpose of code coverage

   Code coverage shows which parts of your code are run when tests execute.

2. Step 2: Identify what code coverage measures

   It measures the percentage of code lines or branches tested, not speed or size.

3. Final Answer:

   How much of the code is executed by tests -> Option A

4. Quick Check:

   Code coverage = executed code percentage [OK]

Hint: Code coverage = tested code parts percentage [OK]

Common Mistakes:

• Confusing coverage with performance
• Thinking coverage measures user count
• Assuming coverage measures file size

2. Which command is commonly used to run tests with coverage in a Node.js project using nyc?

easy

A. nyc node test.js

B. nyc mocha

C. node --coverage test.js

D. npm run coverage

Solution

1. Step 1: Recall nyc usage with test runners

   nyc is a tool that wraps test commands like mocha to collect coverage.

2. Step 2: Identify correct syntax

   Running nyc mocha runs mocha tests with coverage collection.

3. Final Answer:

   nyc mocha -> Option B

4. Quick Check:

   nyc + test runner = coverage run [OK]

Hint: Use nyc before test command to collect coverage [OK]

Common Mistakes:

• Using nyc without a test runner
• Trying node --coverage (not standard)
• Assuming npm run coverage always exists

3. Given this code and test, what coverage report will nyc show for the function add?

function add(a, b) {
  if (a > 0) {
    return a + b;
  } else {
    return 0;
  }
}

// Test
add(2, 3);

medium

A. 75% coverage - partial lines executed

B. 100% coverage - all lines executed

C. 0% coverage - function not called

D. 50% coverage - else branch not executed

Solution

1. Step 1: Analyze which branches run

   The test calls add(2, 3), so the if condition (a > 0) is true, running the first return.

2. Step 2: Identify uncovered code

   The else branch is never executed, so that part is not covered.

3. Final Answer:

   50% coverage - else branch not executed -> Option D

4. Quick Check:

   Uncovered else branch = 50% coverage [OK]

Hint: Check if all branches run to get full coverage [OK]

Common Mistakes:

• Assuming all code runs if function is called once
• Ignoring branches in coverage
• Confusing line coverage with function call

4. You ran nyc mocha but the coverage report shows 0% coverage. What is the most likely cause?

medium

A. The source files are excluded in nyc config

B. nyc was not installed

C. Mocha is not compatible with nyc

D. Tests did not run any code

Solution

1. Step 1: Understand why coverage can be zero

   If source files are excluded in nyc config, coverage won't track them.

2. Step 2: Check other options

   Tests running but no coverage means exclusion is likely; nyc installed and mocha compatible.

3. Final Answer:

   The source files are excluded in nyc config -> Option A

4. Quick Check:

   Excluded files cause zero coverage [OK]

Hint: Check nyc config excludes before blaming tests [OK]

Common Mistakes:

• Assuming tests never ran
• Ignoring nyc config exclusions
• Thinking nyc and mocha are incompatible

5. You want to improve coverage for this function:

function checkValue(x) {
  if (x) {
    return 'Yes';
  } else {
    return 'No';
  }
}

Your tests only call checkValue(true). What change will increase coverage?

hard

A. Add a test calling checkValue('Yes')

B. Add a test calling checkValue(1)

C. Add a test calling checkValue(false)

D. No change needed, coverage is already 100%

Solution

1. Step 1: Identify which branches are tested

   Calling checkValue(true) runs the if branch only, not the else branch.

2. Step 2: Determine how to cover else branch

   Passing false triggers the else branch, increasing coverage.

3. Final Answer:

   Add a test calling checkValue(false) -> Option C

4. Quick Check:

   Test both true and false for full branch coverage [OK]

Hint: Test both true and false to cover all branches [OK]

Common Mistakes:

• Testing other truthy values
• Assuming one test covers all branches
• Ignoring falsy values in coverage