Skip to content

automate-manual-test-cases: investigate page, run tests, ask for missing secrets - #150

Open
DavertMik wants to merge 1 commit into
masterfrom
fix/automate-investigate-run-ask
Open

automate-manual-test-cases: investigate page, run tests, ask for missing secrets#150
DavertMik wants to merge 1 commit into
masterfrom
fix/automate-investigate-run-ask

Conversation

@DavertMik

@DavertMik DavertMik commented Jul 5, 2026

Copy link
Copy Markdown
Contributor

Closes three gaps that let the agent ship unverified automation (guessed selectors, code that never ran, silent about a missing token).

Changes

  • Step 1.4 "Investigate the Live Target Page" (new) — open the page and read the real DOM before writing selectors; confirm the feature is where you think it is. No browser → base on existing POMs and mark unverified selectors ⚠️.
  • Step 4.1 → three-state outcome (passed / failed / blocked). A run that errors before any test executes (missing env, build/init) is blocked, not done, and must be reported as the headline — not a footnote under "done".
  • Missing credential = blocker — STOP and ask the user; never assume a secret. Carved out of the "prefer assumptions over questions" bias.
  • Examples — removed premature Test passed!/All done!; added a "Blocked by a Missing Credential" example.

🤖 Generated with Claude Code

…ing secrets

Close three gaps that let the agent ship unverified automation:

- Add Step 1.4 "Investigate the Live Target Page" — open the page and read
  the real DOM before writing selectors; never invent them from docs or a
  different page.
- Make Step 4.1 a three-state outcome (passed/failed/blocked). A run that
  errors before executing (missing env, build/init) is blocked, not done,
  and must be the headline, not a footnote.
- Treat a missing credential/env var as a blocker: STOP and ask the user;
  never assume a secret. Carve this out of the "minimize questions" bias.
- Fix examples that modeled premature "Test passed!/All done!" and add a
  "Blocked by a Missing Credential" example.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@DavertMik
DavertMik force-pushed the fix/automate-investigate-run-ask branch from a1bf729 to b6b4108 Compare July 5, 2026 22:23

#### 1.4 Investigate the Live Target Page

**Never write UI automation from documents and code alone.** Locators invented from a manual test case, a description, or a *different* page are guesses — they will not run. Before writing selectors for a page, open that page and read its real DOM.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't like this rule...
I think there are cases where generating autotests without actually running app is ok

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants