testeiya 0.8.0 → 0.8.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/package.json +1 -1
  2. package/skills/skills.lock.json +1 -1
  3. package/skills/testomatio/test-management/qa-write-test-cases/SKILL.md +11 -4
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "testeiya",
3
- "version": "0.8.0",
3
+ "version": "0.8.1",
4
4
  "description": "AI testing agent — QA-focused coding agent for manual and automated tests",
5
5
  "type": "module",
6
6
  "license": "MIT",
package/skills/skills.lock.json CHANGED
@@ -3,7 +3,7 @@
3
3
  {
4
4
  "source": "testomatio/skills",
5
5
  "ref": null,
6
- "sha": "f971b5264682260d0257e2e21f1dfa20836fe8d3",
6
+ "sha": "050ece13c42d3bc0f0020336aabebe21fe62cb41",
7
7
  "folder": "testomatio",
8
8
  "skills": [
9
9
  "automate-manual-test-cases",
package/skills/testomatio/test-management/qa-write-test-cases/SKILL.md CHANGED
@@ -40,7 +40,7 @@ References:
40
40
 
41
41
  1. Gather context and show sources — approval gate
42
42
  2. Ask for coverage scope — approval gate
43
- 3. Ask for role — approval gate; skipped for smoke
43
+ 3. Ask for role if any test cases for the feature exist; always skipped for smoke
44
44
  4. Generate checklist — approval gate
45
45
  5. Generate detailed test cases
46
46
  6. Show summary
@@ -132,13 +132,20 @@ Happy path, key negative and common edge cases
132
132
  Full coverage incl. error states, boundaries, and security/perf/i18n where relevant
133
133
 
134
134
  **4. ✏️ Other**
135
- Proceed to specific role selection, type a number of tests, or describe scope in your own words
135
+ Type a number of tests, or describe scope in your own words
136
136
  ```
137
137
 
138
138
  ### Step 3: Ask for role
139
139
 
140
- - If the user picked 🚀 Smoke in Step 2: **skip this step** — auto-apply ⚙️ default and go straight to Step 4. A smoke suite is too small to benefit from a specialized role.
141
- - Otherwise show the roles (markdown table with name and short description) and ask the user to pick one. Recommend a role based on context.
140
+ Ask for a role only when Step 1 found existing test cases for the feature under test. The basics are already covered, so the user may want a specific angle.
141
+
142
+ Also skip this step for "smoke" scope.
143
+
144
+ If the user already named a role or focus (in the prompt or via ✏️ Other in Step 2, e.g. "security edge cases"), apply the matching role without asking.
145
+
146
+ When ask for a role:
147
+
148
+ - Show the roles (markdown table with name and short description) and ask the user to pick one. Recommend a role based on context and on what the existing test cases don't cover yet.
142
149
  - Use ⚙️ default if the user does not specify a role.
143
150
  - If the user selects 🔧 other, ask them to define a custom role.
144
151
  - If you show only some roles, add a "Show all available roles" option: