For QA leads who want every run to test an area the way the team does.
Your setup
- A checkout flow with checks your team always does: a test card, tax on the total, a coupon, the order in the order history.
- People and runs test it in slightly different ways.
- You want one written procedure that runs and the chat follow.
Say this to Certyn
Write a skill "How we test checkout": pay with our test card, check the tax on the total, try the TEST10 coupon, and check the order shows in My Orders. Runs should use it whenever they test checkout.
What Certyn does
- Checks the team's skill list, so it does not make a second checkout skill.
- Writes the full procedure in Markdown: when it applies, steps, test data, expected results, and what not to do (for example, never use a real card).
- Shows you the whole text and asks before it saves.
- Saves it (
app.skill.update) with a name and a one-line note that says when to load it, for example Load when a test touches the cart, payment or order confirmation. - To change it later, say "add the PayPal step to the checkout skill". Certyn saves the whole new text.
How runs and the chat use it
- Every run and chat sees each team skill as one line: its key and its note. When the task fits the note, it loads the full text (
app.skill.get). - To give every run and chat the full text from the start, pin it: Knowledge → Skills, edit the skill, check Pin to every run. All pinned skills together can hold 4,000 characters.
What you get
- Runs and the chat test checkout the same way each time.
- One place to change the procedure.
Limits
- Skills are shared by all projects in the workspace. Name the app in the note.
- Every team skill is listed to the chat and to all runs, whether you save it for runs or for the chat. The note decides when it is loaded, so make it specific.
- The chat cannot pin or delete a skill. Do that on Knowledge → Skills.
- A name has up to 50 characters, a note up to 250.
- A skill guides the method. It does not change a run's goal or scope. Rules that must always hold, like "a cart total is never negative", belong in the wiki.