OBJECTIVE

Define explicit acceptance rules for a small local form or CLI endpoint.

TIME PLAN

Prepare 20m · Build 110m · Verify 30m · Document 20m

Working boundary

Work only inside the folder created by Smartphone-Academy.py prepare input-validation. Use the supplied samples or systems you personally administer.

Prepare the Termux workspace

Open Termux in the Academy root and prepare this lab with the local companion. It creates safe samples, notes and evidence files under your Termux account.

Android + Termuxpython Smartphone-Academy.py prepare input-validationNo root. Use the supplied files and keep the workspace under $HOME.

Practical mission

  1. Specify type, length, format and allowed range
  2. Distinguish validation from output encoding
  3. Create boundary tests around every numeric or length limit
  4. Return useful errors without echoing secrets
EVIDENCE TO PRODUCE

A validation matrix with valid, invalid, boundary and ambiguous examples.

Quality gate

The deliverable states a clear scope and date for Design Input Validation.
A second learner can reproduce the commands and paths.
Original samples remain unchanged and verifiable.
Limitations are recorded beside the conclusions.

Analyst reflection

Which result from “Return useful errors without echoing secrets” would need more evidence before it could support an operational decision?

Complete in Termux

After checking the evidence, run python Smartphone-Academy.py complete input-validation. Progress is stored locally in the Termux home directory.

13 · Web & Secure Coding

Continue learning

Back to Smartphone Academy