Browser agents: test your site the way the agent sees it|INEMA.CLUB-PRO

Lesson 8 · 20 min

The task battery for your site (map + generator)

Time to put it together: the tasks that matter on your site, each with a contract, steps, and what to expect, in a battery that the dry-run robot runs on every change and that your agent can run whenever you want. conferir-bateria.mjs tells you if it is ready; the map and the generator organize what is missing.

Start the lesson
A test bench with a dark monitor showing a list of checked tasks and an industrial robot in the background, neutral light.

In this lesson you will

  1. 1The battery template and what the checker requires
  2. 2At least one task that has to stop
  3. 3Run it against your local site
  4. 4The plan with dates

Goal: build the task battery for your site and check that each task has a contract, proof, and stop.

01The course map

Four steps, the exercises in each one, and what each step delivers. Tap an exercise to see its "done when".

Day 1See

lessons 1 to 3

3 exercises

The ready-made kit, your site's snapshot, and the console and network errors.

View the lesson
Day 2Consume

lesson 4

3 exercises

The agent with and without the API, and the annotated origin test.

View the lesson
Day 3Contract

lesson 5

2 exercises

Two complete contracts, one of them for your site.

View the lesson
Day 4Test

lessons 6 to 8

2 exercises

Your site's battery running, with the result saved to a file.

View the lesson
At the end of the courseA task battery for your site that runs on every change and saves the result, with the stops in the right places.
10 of 19
Click an exercise to see what to do and the "done when".
  1. 1/5

    See

    Agent map, Playwright MCP, and DevTools MCP against the kit and against your site.

  2. 2/5

    Consume

    Requires step 1. Discovery, annotations, fallback, and iframes, with an experimental label.

  3. 3/5

    Contract

    Goal, limits, proof, and stop, checked by the script.

  4. 4/5

    Test

    Battery in the dry run, your agent once, the limits, and your site's battery.

  5. 5/5

    The whole course

    See, consume, contract, and test. Each step has exercises with an expected output; the battery brings it all together.

Suggested order: each step uses the kit or the contract from the previous one.

02From the template to your battery

Four decisions.

1. Which tasks

The ones that make money or cause headaches: finding a price, seeing available times, getting to the contact page. Start read-only.

Each task is a contract: a goal tied to the page, limits with a "no", proof in quotes, a stop with a number.

03The battery checker

The kit's template doesn't pass yet (one task, no stop); the limits battery passes.

File · kit/modelo-bateria.json
{
  "site": "http://127.0.0.1:8000/",
  "tarefas": [
    {
      "id": "t1-trocar",
      "objetivo": "Na página [página].html, trocar por: o que a pessoa quer conseguir nesta página.",
      "limites": "Trocar por: o que o agente pode fazer. Não clicar em Comprar nem em Confirmar.",
      "prova": { "texto": "trocar pelo texto que aparece quando deu certo" },
      "parada": "Pare se aparecer login, verificação ou confirmação. Pare depois de 10 ações.",
      "espera": "ok",
      "passos": [
        { "abrir": "index.html" },
        { "preencher": ["Rótulo do campo", "valor"] },
        { "clicar": "Texto do botão" }
      ]
    }
  ]
}
Terminal · copy the template and check
cd ~/projetos/formacao-webmcp-navegador-v72/kit
cp modelo-bateria.json minha-bateria.json
node conferir-bateria.mjs minha-bateria.json; echo "saída: $?"
Terminal · check a finished battery
cd ~/projetos/formacao-webmcp-navegador-v72/kit
node conferir-bateria.mjs limites.json; echo "saída: $?"
Example from the repository
  só 1 tarefas (mínimo 3)
  nenhuma tarefa com espera "parar" (inclua login, verificação ou confirmação)
bateria com 2 problemas · minha-bateria.json
saída: 1

Two gaps: only one task and no stop. This is the starting point for E1.

04Practice

Your task battery, checked and running. Each exercise has a "done when".

E1 · Build the battery

30 min

Complete minha-bateria.json with 3 to 6 tasks from your site, one of them with "espera": "parar". Replace the site with your project's local address.

Done when: node conferir-bateria.mjs minha-bateria.json → bateria ok: N tarefas · 4 partes em todas · P com parada esperada and saída: 0.

E2 · Run it against your site

15 min

With your site running locally, run the battery. Each ✗ becomes a line in your plan: is it a bug in the site, in the HTML, or in the battery?

Done when: node rodar-bateria.mjs minha-bateria.json → N tarefas · N como esperado and saída: 0, with resultados/minha-bateria.jsonl saved.

05Generate your plan with dates

Pick a start date and how much time you have per week.

06Lesson quiz

Question 1 of 3

The checker rejected your battery with "nenhuma tarefa com espera parar". Why does it require that?skill

07In three sentences

Your site's battery3 to 6 tasks, each with a contract, steps, and what you expect.
At least one stopProves the test stops at login, verification, or confirmation.
Runs every timeThe dry-run robot after every change; your agent whenever you want, checked by format.

Going further

Course kit: conferir-bateria.mjs and modelo-bateria.jsonNext course in the program: 4 · Security and trust between site and agentWebMCP Area: the whole program
Previous lessonBack to the course start