# How I use a stopwatch with laps for small tests

A beginner-friendly guide to using a chronometer, laps, elapsed time, and simple manual measurements.

- Date: 2026-09-27
- URL: https://ilham.dev/posts/how-to-use-a-stopwatch-with-laps-for-small-tests/
- Markdown: https://ilham.dev/posts/how-to-use-a-stopwatch-with-laps-for-small-tests/index.md
- Tags: stopwatch, time, testing, tools
- Reading time: 2 min


A chronometer is useful for quick manual timing when a full benchmark is unnecessary.

The [Chronometer](/tools/chronometer/) tool handles the repetitive part so I can focus on checking whether the result makes sense.

## The simple idea

A chronometer is useful for quick manual timing when a full benchmark is unnecessary.

I still treat the output as something to review, especially when it affects money, dates, privacy, or production data.

## Step 1: Start the timer when the action begins

Start the timer when the action begins.

## Step 2: Use laps for repeated steps

Use laps for repeated steps.

## Step 3: Stop when the action ends

Stop when the action ends.

## Step 4: Compare lap times

Compare lap times.

## Step 5: Repeat the measurement if precision matters

Repeat the measurement if precision matters.

## Step 6: Avoid using manual timing for very small operations

Avoid using manual timing for very small operations.

## Step 7: Use a proper benchmark for code performance decisions

Use a proper benchmark for code performance decisions.

## My checklist

Before I trust the result, I check:

- Start the timer when the action begins.
- Use laps for repeated steps.
- Stop when the action ends.
- Compare lap times.
- Repeat the measurement if precision matters.
- Avoid using manual timing for very small operations.
- Use a proper benchmark for code performance decisions.

A small tool is most useful when it makes the work visible and easy to verify.