Async test patterns in Deno - Performance & Optimization

Performance: Async test patterns

MEDIUM IMPACT

This affects test execution speed and responsiveness during asynchronous operations in tests.

Writing asynchronous tests that wait for promises to resolve

Deno

Deno.test("good async test", async () => {
  const response = await fetch("https://example.com");
  const data = await response.json();
  if (!data) throw new Error("No data");
});

Using async/await ensures the test runner waits for completion, improving reliability and responsiveness.

📈 Performance GainNon-blocking test execution with predictable completion, reducing retries and wasted CPU.

Writing asynchronous tests that wait for promises to resolve

Deno

Deno.test("bad async test", () => {
  const result = fetch("https://example.com");
  const data = result.then(res => res.json());
  // No await, test ends before promise resolves
  if (!data) throw new Error("No data");
});

Test does not wait for the async operation to finish, causing false positives or errors.

📉 Performance CostBlocks test runner unpredictably, causing flaky test results and wasted retries.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Callback without await	N/A	N/A	N/A	[X] Bad
Sequential await	N/A	N/A	N/A	[!] OK
Parallel await with Promise.all	N/A	N/A	N/A	[OK] Good

Rendering Pipeline

Async test patterns affect how the test runner schedules and waits for asynchronous code, impacting the event loop and task queue.

→Task Scheduling

→Event Loop

→Test Runner Execution

⚠️ BottleneckImproper async handling causes blocking or premature test completion, delaying event loop cycles.

Core Web Vital Affected

INP

This affects test execution speed and responsiveness during asynchronous operations in tests.

Optimization Tips

1Always use async/await to ensure tests wait for async operations.

2Use Promise.all to run multiple async calls in parallel for faster tests.

3Avoid callback-only patterns that can cause premature test completion.

Performance Quiz - 3 Questions

What is the main performance benefit of using async/await in Deno tests?

A It makes tests run faster by skipping async operations.

B It ensures tests wait for async operations to finish, improving reliability and responsiveness.

C It reduces the size of the test code bundle.

D It automatically caches test results for faster reruns.

DevTools: Performance

How to check: Run tests with Deno and open DevTools Performance panel. Record while tests run. Look for long blocking tasks or idle waits.

What to look for: Check for long tasks blocking the event loop or gaps indicating premature test completion.

Practice

1. What is the main reason to use async and await in Deno test functions?

easy

A. To automatically retry failed tests

B. To make tests run faster by skipping delays

C. To avoid writing any assertions in tests

D. To handle code that involves waiting or delays smoothly

Solution

1. Step 1: Understand async/await purpose

   Async/await lets code wait for operations like fetching data or timers before continuing.

2. Step 2: Connect async/await to testing

   In tests, async/await ensures the test waits for the code under test to finish before checking results.

3. Final Answer:

   To handle code that involves waiting or delays smoothly -> Option D

4. Quick Check:

   Async tests wait properly = A [OK]

Hint: Async tests wait for promises to resolve before asserting [OK]

Common Mistakes:

• Thinking async makes tests faster
• Skipping await and causing false positives
• Confusing async with retry logic

2. Which of the following is the correct way to declare an async test in Deno?

easy

A. Deno.test(() => { await someAsyncFunc(); });

B. Deno.test(async () => { await someAsyncFunc(); });

C. async Deno.test(() => { someAsyncFunc(); });

D. Deno.test(async function someAsyncFunc() {});

Solution

1. Step 1: Check async function syntax in test

   The test function must be declared async to use await inside it.

2. Step 2: Validate each option

   Deno.test(async () => { await someAsyncFunc(); }); correctly declares an async arrow function with await inside. Deno.test(() => { await someAsyncFunc(); }); misses async keyword. async Deno.test(() => { someAsyncFunc(); }); has invalid syntax. Deno.test(async function someAsyncFunc() {}); passes an async function but without calling it properly.

3. Final Answer:

   Deno.test(async () => { await someAsyncFunc(); }); -> Option B

4. Quick Check:

   Async arrow function with await = A [OK]

Hint: Async test functions need async keyword before () => [OK]

Common Mistakes:

• Omitting async keyword before arrow function
• Trying to await outside async function
• Incorrect async function syntax in test

3. What will be the output when running this Deno test?

import { assertEquals } from "https://deno.land/std/testing/asserts.ts";

Deno.test("delayed test", async () => {
  const result = await new Promise((resolve) => setTimeout(() => resolve(42), 100));
  assertEquals(result, 42);
});

medium

A. Test passes after 100ms delay

B. Test fails immediately with assertion error

C. SyntaxError due to incorrect async usage

D. Test times out and fails

Solution

1. Step 1: Analyze the async test code

   The test waits 100ms using a Promise with setTimeout, then resolves with 42.

2. Step 2: Check assertion correctness

   The test asserts that the resolved value is 42, which matches the expected value.

3. Final Answer:

   Test passes after 100ms delay -> Option A

4. Quick Check:

   Awaited promise resolves correctly = D [OK]

Hint: Await promises to ensure test waits for async results [OK]

Common Mistakes:

• Expecting immediate test pass without await
• Confusing assertion values
• Assuming syntax error without checking code

4. Identify the error in this Deno async test code:

import { assertEquals } from "https://deno.land/std/testing/asserts.ts";

Deno.test("broken test", () => {
  const result = await Promise.resolve(10);
  assertEquals(result, 10);
});

medium

A. assertEquals is not imported correctly

B. Promise.resolve cannot be awaited

C. Missing async keyword before the test function

D. Test name is invalid

Solution

1. Step 1: Check async usage in test function

   The test function uses await but is not declared async, which causes a syntax error.

2. Step 2: Verify other parts

   assertEquals is imported correctly, Promise.resolve can be awaited, and test name is valid.

3. Final Answer:

   Missing async keyword before the test function -> Option C

4. Quick Check:

   Await requires async function = B [OK]

Hint: Add async before test function to use await inside [OK]

Common Mistakes:

• Forgetting async keyword with await
• Assuming Promise.resolve can't be awaited
• Misreading import statements

5. You want to test a function fetchData() that returns a promise resolving to an object. Which pattern correctly tests it with Deno's async test and handles errors gracefully?

hard

A. Deno.test("fetchData test", async () => {
try {
const data = await fetchData();
assert(data !== null);
} catch {
throw new Error("fetchData failed");
}
});

B. Deno.test("fetchData test", () => {
fetchData().then(data => assert(data !== null));
});

C. Deno.test("fetchData test", async () => {
const data = await fetchData();
assert(data !== null);
});

D. Deno.test("fetchData test", async () => {
fetchData().catch(() => {});
assert(true);
});

Solution

1. Step 1: Understand async test with error handling

   Using async/await with try/catch allows catching errors and failing the test properly.

2. Step 2: Evaluate each option

   Deno.test("fetchData test", async () => { const data = await fetchData(); assert(data !== null); }); lacks error handling, so test may silently fail. Deno.test("fetchData test", () => { fetchData().then(data => assert(data !== null)); }); is not async and may finish before promise resolves. Deno.test("fetchData test", async () => { try { const data = await fetchData(); assert(data !== null); } catch { throw new Error("fetchData failed"); } }); uses async/await with try/catch correctly. Deno.test("fetchData test", async () => { fetchData().catch(() => {}); assert(true); }); ignores errors and asserts true regardless.

3. Final Answer:

   Deno.test("fetchData test", async () => { try { const data = await fetchData(); assert(data !== null); } catch { throw new Error("fetchData failed"); } }); -> Option A

4. Quick Check:

   Async test with try/catch for errors = C [OK]

Hint: Use async/await with try/catch to catch errors in tests [OK]

Common Mistakes:

• Not awaiting promises in tests
• Ignoring errors causing false passes
• Using then() without returning promise in test