📖 Scenario: You are building a simple utility module in Deno that includes a function to add two numbers. To ensure your code works correctly, you want to write test functions using Deno's built-in testing framework.
🎯 Goal: Write a test function in Deno that checks if the add function correctly adds two numbers.
📋 What You'll Learn
Create a function called add that takes two numbers and returns their sum.
Create a test function using Deno's Deno.test to verify the add function.
Use assertEquals from std/testing/asserts.ts to check the result.
Name the test function testAddFunction.
💡 Why This Matters
🌍 Real World
Writing test functions helps catch bugs early and ensures your code works as expected before deployment.
💼 Career
Testing skills are essential for software developers to maintain code quality and reliability in professional projects.
Progress0 / 4 steps
1
Create the add function
Write a function called add that takes two parameters a and b and returns their sum using return a + b.
Deno
Hint
Define a function named add with two parameters and return their sum.
2
Import assertEquals from Deno standard library
Add an import statement to import assertEquals from "https://deno.land/std@0.195.0/testing/asserts.ts".
Deno
Hint
Use an import statement to bring in assertEquals from the Deno standard library URL.
3
Write the test function testAddFunction
Write a test function using Deno.test named testAddFunction. Inside it, call assertEquals(add(2, 3), 5) to check if add(2, 3) returns 5.
Deno
Hint
Use Deno.test with a name and a function that calls assertEquals to check the result.
4
Complete the test setup
Ensure the test function is correctly closed with parentheses and braces, and the code is ready to run with deno test.
Deno
Hint
Make sure the test function is syntactically complete and ready to run.
Practice
(1/5)
1. What is the main purpose of using deno.test in your code?
easy
A. To write test functions that check if code works correctly
B. To run the main application server
C. To format code automatically
D. To deploy code to the cloud
Solution
Step 1: Understand the role of deno.test
deno.test is used to define test functions that verify code behavior.
Step 2: Differentiate from other tasks
Running servers, formatting, or deploying are not related to deno.test.
Final Answer:
To write test functions that check if code works correctly -> Option A
Quick Check:
Test functions = deno.test usage [OK]
Hint: Tests check code correctness using deno.test [OK]
Common Mistakes:
Confusing test functions with running servers
Thinking deno.test formats code
Assuming deno.test deploys code
2. Which of the following is the correct syntax to define a test function in Deno?
easy
A. test(() => { /* test code */ });
B. test.deno(() => { /* test code */ });
C. deno.runTest(() => { /* test code */ });
D. deno.test(() => { /* test code */ });
Solution
Step 1: Recall correct Deno test syntax
The correct way to define a test is deno.test(() => { ... }).
Step 2: Identify incorrect options
Options B, C, and D use wrong method names or missing namespace.
Final Answer:
deno.test(() => { /* test code */ }); -> Option D
Quick Check:
Correct test syntax = deno.test [OK]
Hint: Use deno.test() exactly to define tests [OK]
Common Mistakes:
Swapping method names like test.deno or deno.runTest
Omitting 'deno.' prefix
Using just test() without import or context
3. What will be the output when running this test code in Deno?
import { assertEquals } from "https://deno.land/std/testing/asserts.ts";
deno.test("sum test", () => {
const result = 2 + 3;
assertEquals(result, 5);
});
medium
A. Runtime error: deno.test is undefined
B. Test fails with assertion error
C. Test passes with no errors
D. Syntax error due to import
Solution
Step 1: Analyze the test logic
The test calculates 2 + 3 and checks if it equals 5, which is true.
Step 2: Check for syntax or runtime issues
The import and usage of deno.test and assertEquals are correct.
Final Answer:
Test passes with no errors -> Option C
Quick Check:
Correct assertion means test passes [OK]
Hint: Correct assertEquals means test passes [OK]
Common Mistakes:
Assuming test fails when assertion is true
Thinking import causes syntax error
Confusing runtime errors with correct usage
4. Identify the error in this Deno test code:
import { assertEquals } from "https://deno.land/std/testing/asserts.ts";
deno.test("check value", () => {
const value = 10;
assertEquals(value, "10");
});
medium
A. Type mismatch causes assertion failure
B. Missing async keyword in test function
C. Incorrect import URL for assertEquals
D. deno.test requires a name and function separately
Solution
Step 1: Check assertion parameters
The test compares number 10 with string "10", which are not equal.
Step 2: Confirm other syntax correctness
Import URL and test function syntax are correct; async is not required here.
Final Answer:
Type mismatch causes assertion failure -> Option A
Quick Check:
assertEquals fails if types differ [OK]
Hint: assertEquals fails if types differ exactly [OK]
Common Mistakes:
Thinking async is always needed
Assuming string and number are equal
Believing import URL is wrong
5. You want to write a test in Deno that checks if a function getUserName(id) returns a non-empty string for valid IDs. Which test function is best to write?
hard
A. deno.test("user name test", () => { const name = getUserName(1); assertEquals(typeof name, "number"); });
B. deno.test("user name test", () => { const name = getUserName(1); assert(name.length > 0); });
C. deno.test("user name test", () => { const name = getUserName(1); assertEquals(name, ""); });
D. deno.test("user name test", () => { const name = getUserName(1); assertEquals(name, null); });
Solution
Step 1: Understand the test goal
The test should verify the returned name is a non-empty string.
Step 2: Evaluate each option
deno.test("user name test", () => { const name = getUserName(1); assert(name.length > 0); }); checks if length > 0, which matches the goal. Options A, B, and D check for number type, empty string, or null, which are incorrect.
Final Answer:
deno.test("user name test", () => { const name = getUserName(1); assert(name.length > 0); }); -> Option B
Quick Check:
Check non-empty string with length > 0 [OK]
Hint: Check string length > 0 to confirm non-empty [OK]
Common Mistakes:
Checking for empty string instead of non-empty
Checking wrong type like number or null
Using assertEquals with wrong expected value
Recommended
Ready to prove it?
Pass the test and this pattern moves unknownstrongwhile earning +1 Grip toward your certificate.