DiscoveryVIP / Apps Script AcademyHelp

89. Testing functions and spreadsheet data

Module 18 · 20 minutes · Lesson 88; earlier service and JavaScript fundamentals

Open Interactive Lesson

Discover

How can you use testing functions and spreadsheet data without changing the wrong data?

Predict

Which values or resources will change, and which should stay unchanged? Write your prediction before execution.

Understand

A useful test specifies input, expected output and an observable failure. Test boundaries and invalid types as well as typical values. Compare arrays by content rather than object identity. Keep an independent oracle instead of deriving the expected answer from the same function being tested. This small validator separates required text from truthiness.

Example 1: Working automation

Whitespace fails after trimming and numbers fail the type guard, so the contract covers more than one happy input.

function main() {
  console.log(validName("Alex"));
  console.log(validName("   "));
  console.log(validName(42));
}
function validName(value) {
  return typeof value === "string" && value.trim().length > 0;
}
Important line explanations
Line 1: function main() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 2: console.log(validName("Alex"));
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 3: console.log(validName(" "));
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 4: console.log(validName(42));
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 5: }
Close the current block. Indentation makes scope and the function boundary visible.
Line 6: function validName(value) {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 7: return typeof value === "string" && value.trim().length > 0;
End this function and pass its value to the caller; logging alone does not return a result.
Line 8: }
Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
  "logs": [
    "true",
    "false",
    "false"
  ],
  "error": null,
  "resource": "logs",
  "value": null
}

Example 2: Investigate a reproducible failure

Predict the effect of value.length > 0 and identify the first mismatch. This example is intentionally faulty.

function main() {
  console.log(validName("Alex"));
  console.log(validName("   "));
  console.log(validName(42));
}
function validName(value) {
  return typeof value === "string" && value.length > 0;
}
Important line explanations
Line 1: function main() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 2: console.log(validName("Alex"));
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 3: console.log(validName(" "));
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 4: console.log(validName(42));
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 5: }
Close the current block. Indentation makes scope and the function boundary visible.
Line 6: function validName(value) {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 7: return typeof value === "string" && value.length > 0;
End this function and pass its value to the caller; logging alone does not return a result.
Line 8: }
Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
  "logs": [
    "true",
    "true",
    "false"
  ],
  "error": null,
  "resource": "logs",
  "value": null
}

Example 3: Separate setup from execution and inspect repeat behavior

Call the same named operation twice. Compare outputs and resource counts to learn whether this operation is idempotent. Repeated creation is deliberately visible; real exports require a rerun policy.

function lessonAction() {
  console.log(validName("Alex"));
  console.log(validName("   "));
  console.log(validName(42));
}
function validName(value) {
  return typeof value === "string" && value.trim().length > 0;
}
function main() {
  lessonAction();
  lessonAction();
}
Important line explanations
Line 1: function lessonAction() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 2: console.log(validName("Alex"));
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 3: console.log(validName(" "));
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 4: console.log(validName(42));
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 5: }
Close the current block. Indentation makes scope and the function boundary visible.
Line 6: function validName(value) {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 7: return typeof value === "string" && value.trim().length > 0;
End this function and pass its value to the caller; logging alone does not return a result.
Line 8: }
Close the current block. Indentation makes scope and the function boundary visible.
Line 9: function main() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 10: lessonAction();
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 11: lessonAction();
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 12: }
Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
  "logs": [
    "true",
    "false",
    "false",
    "true",
    "false",
    "false"
  ],
  "error": null,
  "resource": "logs",
  "value": null
}

Example 4: Add a diagnostic boundary around the operation

Observe start, successful completion or a rethrown failure. This optional professional pattern adds error context without swallowing the error or rolling back changes.

function lessonAction() {
  console.log(validName("Alex"));
  console.log(validName("   "));
  console.log(validName(42));
}
function validName(value) {
  return typeof value === "string" && value.trim().length > 0;
}
function main() {
  console.log("Start: Testing functions and spreadsheet data");
  try { lessonAction(); console.log("Completed operation"); }
  catch(error) { console.error("Failed operation: " + error.message); throw error; }
}
Important line explanations
Line 1: function lessonAction() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 2: console.log(validName("Alex"));
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 3: console.log(validName(" "));
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 4: console.log(validName(42));
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 5: }
Close the current block. Indentation makes scope and the function boundary visible.
Line 6: function validName(value) {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 7: return typeof value === "string" && value.trim().length > 0;
End this function and pass its value to the caller; logging alone does not return a result.
Line 8: }
Close the current block. Indentation makes scope and the function boundary visible.
Line 9: function main() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 10: console.log("Start: Testing functions and spreadsheet data");
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 11: try { lessonAction(); console.log("Completed operation"); }
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 12: catch(error) { console.error("Failed operation: " + error.message); throw error; }
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 13: }
Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
  "logs": [
    "Start: Testing functions and spreadsheet data",
    "true",
    "false",
    "false",
    "Completed operation"
  ],
  "error": null,
  "resource": "logs",
  "value": null
}

Build and test

Repair the supplied script so that: Whitespace fails after trimming and numbers fail the type guard, so the contract covers more than one happy input. Preserve other source data. Checks compare observable output and the named resource, not exact source text.

function main() {
  console.log(validName("Alex"));
  console.log(validName("   "));
  console.log(validName(42));
}
function validName(value) {
  return typeof value === "string" && value.length > 0;
}

Graduated hints

Hint 1

Inspect the operation containing value.length > 0. Compare it with the stated rule and the first mismatch.

Hint 2

The repair concerns value.trim().length > 0. Change only the relevant argument, operator or method; rerun with fresh input.

Hint 3

The reference uses value.trim().length > 0 where the broken source uses value.length > 0. Explain why before applying it.

Reference solution

function main() {
  console.log(validName("Alex"));
  console.log(validName("   "));
  console.log(validName(42));
}
function validName(value) {
  return typeof value === "string" && value.trim().length > 0;
}

Explain and reflect

Which operation proves the intended result in testing functions and spreadsheet data? Which wrong input would expose a weakness, and what would remain unchanged?

Adapt the calculation or validation to a second realistic case. Write its expected result before running. Demonstrate one invalid case and explain whether the side effects should be rolled back or retried.

Troubleshooting

If the console is empty, inspect the logs preview: this script may work through state changes. If the function is missing, select main. For a service error inspect the first failed timeline entry and its arguments. Use Manual unless investigating a trigger. Changing input data also changes the expected result; restore sample data before the authored checks.

Knowledge check

Explain the key method or operator. Give an exact output for a second input, plus one invalid case. Verify the result in the interactive lesson; written explanations need self or educator review.

Optional AI practice

Explain this concept using the source above. Help implement one small extension and define its tests. Review/debug the source using its actual expected output; cite real method references and never claim execution.

Transfer to Google and authorization guide

Next lesson: Quotas, batching, locks and duplicate processing