@supatest/cli 0.0.56 → 0.0.57

package/dist/index.js

@@ -6045,7 +6045,7 @@ var CLI_VERSION;
 var init_version = __esm({
   "src/version.ts"() {
     "use strict";
-    CLI_VERSION = "0.0.56";
+    CLI_VERSION = "0.0.57";
   }
 });
 
@@ -9776,7 +9776,7 @@ Required tags for ALL tests:
 - @priority:critical|high|medium|low \u2014 Test importance
 - @test_type:smoke|e2e|regression|integration|unit \u2014 Classification
 
-Optional: @owner:email, @ticket:PROJ-123, @slow, @flaky, @manual, @key:value
+Optional: @owner:email, @ticket:PROJ-123, @slow, @flaky, @key:value
 
 **Playwright** \u2014 ALWAYS use the native tag property (even if existing tests use title-based tags):
 test("User can login", { tag: ['@id:AUTH-LOGIN-001', '@feature:auth', '@priority:high', '@test_type:e2e'] }, async ({ page }) => { });
@@ -9786,19 +9786,26 @@ it("User can login (@id:AUTH-LOGIN-001 @feature:auth @priority:high @test_type:e
 
 **Existing tests without @id** \u2014 When fixing or modifying a test that has no @id tag, add one. Generate the ID from the feature + a short description, e.g. @id:CHECKOUT-SUBMIT-001.
 
-**Manual test cases** \u2014 Use the @manual tag to mark tests that require human execution. For manual tests, write an empty shell that is skipped so it appears in the test catalog without running automatically:
+**Manual tests** \u2014 When you identify a scenario that requires human execution (e.g. physical device, visual inspection, third-party flow), capture it as a manual test case rather than skipping or omitting it:
 
-Playwright:
-test("Verify checkout flow on mobile device", { tag: ['@id:CHECKOUT-MOBILE-001', '@manual', '@feature:checkout', '@priority:high'] }, async () => {
-  test.skip(true, 'Manual test \u2014 requires human execution');
-});
+1. Draft the test as a markdown file at \`manual-tests/{feature}-{short-title}.md\` using this structure:
+   \`\`\`markdown
+   # {Title}
+   **Priority**: critical|high|medium|low
+   **Tags**: tag1, tag2
 
-WebdriverIO/Other:
-it("Verify checkout flow on mobile device (@id:CHECKOUT-MOBILE-001 @manual @feature:checkout @priority:high)", async () => {
-  pending('Manual test \u2014 requires human execution');
-});
+   ## Preconditions
+   - ...
+
+   ## Steps
+   1. ...
+   2. ...
 
-Manual tests show up in the Supatest dashboard as "Manual" and their results can be recorded through the platform UI.
+   ## Expected Result
+   - ...
+   \`\`\`
+2. Show the draft to the user and ask for confirmation before creating it in Supatest.
+3. On confirmation, use the Supatest MCP \`create-manual-test\` tool to create it (pass \`title\`, \`steps\` as the markdown body, \`priority\`, \`tags\`, and \`folderId\` if relevant).
 
 A test is not complete until it has @id plus the other required tags.
 </test_tagging>`;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@supatest/cli",
-  "version": "0.0.56",
+  "version": "0.0.57",
   "description": "Supatest CLI - AI-powered task automation for CI/CD",
   "type": "module",
   "bin": {