Tests are not finished when they first pass. Requirements change, flows grow, and you notice the check you forgot. This exercise is about editing a test by talking to it. About ten minutes.
Where you do this
The agent chat on the left of the test editor is not only for creating tests. It is where you change them, and the conversation stays with the test — so in six weeks the reasoning behind an odd-looking step is still there.
Step 1 — Add a step
Open your test and ask:
Add a step at the end that verifies the product page shows the price $966.00.Read the reply. It will tell you what it added and where. Then run the test and watch the new step execute.
Step 2 — Change something that already exists
Change this test to use the Boltas 1.5 Ton 5 Star Split AC instead, and update the price check to $965.00.Notice this is one request touching several steps — the click, the product and the price. You did not have to find them yourself.
Step 3 — Ask it to explain itself
Which steps did you change, and why?Do this regularly. It is the fastest way to build confidence in what the tool is doing on your behalf, and it costs nothing.
Step 4 — Undo something
Actually, revert that — put the Boltas 2 Ton 3 Star Split AC back and restore the $966.00 check.The conversation is the audit trail. You can see what changed, in order, with the reasons.
Prompts worth knowing
These are patterns, not magic words. Say it however you like.
| Add coverage | Also verify the product page shows an Add to Cart button. |
| Tighten a check | Make that step check the exact text, not just that it contains it. |
| Loosen a check | That step is too strict — just verify a price is displayed. |
| Timing | This test is failing on timing — extend the page-load timeout. |
| Self-healing | Be more conservative about fixing this test on its own. |
| Split up | Split this into two tests: one for the category, one for the product page. |
| Rename | Rename this test to something that describes what it proves. |
| Explain | What does step 3.1 actually do? |
Two habits worth forming
Ask for one change at a time when it matters. Bundling five edits into one message works, but it makes the reply harder to check and the history harder to read later.
Re-run after every change. A change you have not seen pass is a hypothesis. The agent will often offer to run it for you — say yes.
Checkpoint
You are done when you have changed a test without opening a step editor or touching a selector, and the test still passes.
What you learned
Maintaining a test is a conversation, and the conversation is kept. That is the part that compounds: the test carries its own explanation.