Test execution time analysis in JUnit - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is test execution time analysis?

It is the process of measuring how long tests take to run. This helps find slow tests and improve testing speed.

beginner

How can you measure test execution time in JUnit?

JUnit provides @Test annotation and you can use System.nanoTime() or System.currentTimeMillis() before and after test code to measure duration.

beginner

Why is it important to analyze test execution time?

Because slow tests can delay feedback and reduce productivity. Fast tests help developers find problems quickly and keep code quality high.

intermediate

What is a common tool or method to report test execution times in JUnit?

JUnit test runners often show execution time per test in the console or reports. You can also use listeners or extensions to log times.

intermediate

How can you improve slow tests after analyzing execution time?

You can optimize test code, reduce unnecessary setup, mock slow dependencies, or split large tests into smaller ones.

What does test execution time analysis help identify?

A Test coverage percentage

B Syntax errors in test code

C Missing test cases

D Slow tests that delay feedback

Test execution time analysis focuses on how long tests take to run, helping find slow tests.

Which Java method can be used to measure time in JUnit tests?

A System.nanoTime()

B Thread.sleep()

C System.exit()

D Math.random()

System.nanoTime() returns the current time in nanoseconds, useful for measuring durations.

What is a benefit of fast test execution?

A Increased test flakiness

B Faster feedback to developers

C Longer build times

D More complex test code

Fast tests give quick feedback, helping developers fix issues sooner.

Which JUnit feature can help log test execution times automatically?

A Test listeners or extensions

B JUnit @Ignore annotation

C JUnit @BeforeClass annotation

D JUnit @Deprecated annotation

Listeners or extensions can hook into test lifecycle events to log execution times.

What is a good way to speed up slow tests?

A Add more assertions

B Increase test data size

C Mock slow dependencies

D Run tests sequentially

Mocking slow parts avoids delays and speeds up tests.

Explain how you would measure and analyze test execution time in a JUnit test suite.

Think about timing methods and how to collect results.

Describe strategies to improve test suite performance after finding slow tests.

Focus on making tests simpler and faster.

Practice

1. What is the main purpose of measuring test execution time in JUnit?

easy

A. To automatically fix failing tests

B. To check if tests are written with correct syntax

C. To verify the correctness of test assertions

D. To identify slow tests and improve test suite performance

Solution

1. Step 1: Understand test execution time concept

   Measuring execution time helps find tests that take longer than expected.

2. Step 2: Identify the goal of measuring time

   Knowing slow tests allows developers to optimize or fix them, improving overall test speed.

3. Final Answer:

   To identify slow tests and improve test suite performance -> Option D

4. Quick Check:

   Execution time = find slow tests [OK]

Hint: Execution time helps spot slow tests to speed up runs [OK]

Common Mistakes:

• Confusing execution time with test correctness
• Thinking it fixes tests automatically
• Ignoring performance impact of slow tests

2. Which JUnit code snippet correctly measures the execution time of a test method?

easy

A. long start = System.nanoTime(); // test code here
long end = System.nanoTime(); System.out.println(end - start);

B. long start = System.currentTimeMillis(); // test code here
long end = System.currentTimeMillis(); System.out.println(end - start);

C. int start = System.nanoTime(); // test code here
int end = System.nanoTime(); System.out.println(end - start);

D. int start = System.currentTimeMillis(); // test code here
int end = System.currentTimeMillis(); System.out.println(end - start);

Solution

1. Step 1: Check correct data type for time

   System.nanoTime() returns long, so variables must be long, not int.

2. Step 2: Verify correct method usage

   System.nanoTime() is preferred for measuring elapsed time with better precision.

3. Final Answer:

   long start = System.nanoTime(); // test code here long end = System.nanoTime(); System.out.println(end - start); -> Option A

4. Quick Check:

   Use long + System.nanoTime() for timing [OK]

Hint: Use long type with System.nanoTime() for precise timing [OK]

Common Mistakes:

• Using int instead of long for time variables
• Using System.currentTimeMillis() for high precision timing
• Mixing data types causing compile errors

3. Given the following JUnit test snippet, what will be printed?

long start = System.nanoTime();
Thread.sleep(100);
long end = System.nanoTime();
System.out.println((end - start) / 1_000_000 + " ms");

medium

A. Approximately 100 ms

B. Exactly 100 ms

C. Approximately 0 ms

D. Compilation error due to Thread.sleep

Solution

1. Step 1: Understand Thread.sleep effect

   Thread.sleep(100) pauses the thread for about 100 milliseconds.

2. Step 2: Calculate elapsed time in milliseconds

   Elapsed time = (end - start) in nanoseconds, divided by 1,000,000 converts to milliseconds, close to 100 ms.

3. Final Answer:

   Approximately 100 ms -> Option A

4. Quick Check:

   Sleep 100ms prints ~100 ms [OK]

Hint: Sleep pauses ~100ms, nanoTime difference shows ~100 ms [OK]

Common Mistakes:

• Expecting exact 100 ms (sleep is approximate)
• Confusing nanoseconds with milliseconds
• Thinking Thread.sleep causes compile error

4. Identify the error in this JUnit test measuring execution time:

@Test
void testMethod() {
  long start = System.nanoTime();
  // test code
  long end = System.nanoTime();
  System.out.println(end - start);
}

medium

A. Missing exception handling for test code

B. Using System.nanoTime() is incorrect for timing

C. No error; code correctly measures time

D. Printing time inside test causes test failure

Solution

1. Step 1: Review timing code correctness

   Using System.nanoTime() before and after test code correctly measures elapsed time.

2. Step 2: Check for syntax or runtime errors

   No syntax errors or exceptions are present; printing time is allowed and does not fail test.

3. Final Answer:

   No error; code correctly measures time -> Option C

4. Quick Check:

   System.nanoTime() timing code is valid [OK]

Hint: Timing code with nanoTime and print is valid [OK]

Common Mistakes:

• Assuming print causes test failure
• Thinking exception handling is mandatory here
• Confusing nanoTime with incorrect timing method

5. You want to fail a JUnit test if it runs longer than 500 milliseconds. Which approach correctly implements this using execution time measurement?

hard

A. Use System.currentTimeMillis() and assert elapsed time <= 500 nanoseconds without conversion

B. Record start and end time with System.nanoTime(), then assert elapsed time <= 500_000_000 nanoseconds

C. Print execution time and manually check after test runs

D. Use Thread.sleep(500) inside the test to limit execution time

Solution

1. Step 1: Understand time units and assertion

   System.nanoTime() returns nanoseconds; 500 ms = 500,000,000 ns.

2. Step 2: Implement assertion on elapsed time

   Calculate elapsed = end - start; assert elapsed <= 500_000_000 to fail if too slow.

3. Final Answer:

   Record start and end time with System.nanoTime(), then assert elapsed time <= 500_000_000 nanoseconds -> Option B

4. Quick Check:

   Assert elapsed ≤ 500ms in nanoseconds [OK]

Hint: Convert 500ms to nanoseconds and assert elapsed ≤ that [OK]

Common Mistakes:

• Using Thread.sleep to limit test time
• Not converting time units correctly
• Only printing time without assertion