@nbakka/mcp-appium 3.0.12 → 3.0.13

package/lib/app_context.txt

@@ -18,9 +18,9 @@ IMPORTANT: If the element you looking for is not present you can use swipe
 - sendKeys("locator_key", "string_to_be_passed", Wait.SHORT)
 Figure out dynamic paths like //android.widget.TextView[@text="View 180 Properties"] here 180 is not constant so create a xpath like //android.widget.TextView[contains(@text,"View") and contains(@text,"Properties")]
 For repeating logic, create loops
-Generated code should be pasted in aicode.txt as mentioned below, clear the existing contents of it before copying new code.
-No need to add comments in code and only mention locators that are new and not present in the locator sheet in comments at end of aicode.txt file as shown in sample code below.
-** SAMPLE FILE aicode.txt **
+No need to add comments in code and only mention locators that are new and not present in the locator sheet in comments at end of file as shown in sample code below.
+Automation code has to be generated only for approved test cases
+** SAMPLE TESTCASES Automation code has to be generated only for approved test cases**
 /**
  * Test Method for Nearby Properties Verification on New Project Dedicated Page
  * Verifies that clicking on nearby properties opens the correct detail page

package/lib/server.js

@@ -149,9 +149,9 @@ const createMcpServer = () => {
 
  tool(
    "mobile_learn_current_app_context",
-   "Follow these instructions strictly to navigate through the app. This should be the first step after launching the app and before performing any tests. Provide the Google Sheet name to fetch locatorName and androidLocator from the specified sheet. NOTE: Only use the locator data from the Google Sheet at the end while generating test cases, don't use to navigate through screens",
+   "Follow these instructions strictly to navigate through the app. This should be the first step after launching the app and before performing any tests. Google Sheet name to fetch locatorName and androidLocator from the specified sheet. NOTE: Only use the locator data from the Google Sheet at the end while generating test cases, don't use to navigate through screens",
    {
-     sheetName: zod_1.z.string().describe("The name of the Google Sheet to fetch locator data from"),
+     sheetName: zod_1.z.string().describe("The name of the Google Sheet to fetch locator data from").default("PDP"),
    },
    async ({ sheetName }) => {
      try {

package/lib/testcases-generation-context.txt

@@ -1,3 +1,11 @@
+When asked to generate automation test cases for a jira ticket, the flow is as follows (Should not ask for user input till the last step):
+by using mcp tools
+1. Read the jira summary and description to understand the changes made in the feature.
+2. Look at the figma design link provided in the jira ticket to understand the UI changes
+3. Based on the changes mentioned in the jira summary and description, and the figma design, generate test cases
+4. Approval from user is needed for the generated test cases
+5. Once the test cases are approved by user, learn mobile app context
+6. Generate automation code for the approved test cases or modify existing for linked test files
 generate test cases using jira summary, description and figma image,
 don't wait for extra user input,
 test cases scope should be only for the changes mentioned in jira summary and description,
@@ -20,6 +28,6 @@ for review_testcases and update_testcases_to_tcms tool data should be in this fo
 {"testCases":[["Verify that brochure section is visible under overview tab","Verify brochure section is removed from property tour tab","Modify","SCRUM-TC-1"],
 ["Verify similar properties section is visible under over tab in pdp section","Remove","SCRUM-TC-2"],
 ["Verify Project Brochure section appears above the 'Explore on map' section in Overview tab","New"]]}
-
 for update_testcases_to_tcms tool, send only test cases approved by user
-NOTE: keep polling continously for 10 times max till the test cases are approved by user
+NOTE: keep polling continously for 10 times max till the test cases are approved by user, don't wait for user input
+Automation code has to be generated only for approved test cases

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nbakka/mcp-appium",
-  "version": "3.0.12",
+  "version": "3.0.13",
   "description": "Appium MCP",
   "engines": {
     "node": ">=18"