@nbakka/mcp-appium 3.0.19 → 3.0.20

package/lib/app_context.txt

@@ -1,106 +1,70 @@
 ******** START OF GUIDELINES ********
-You are an expert Appium test case generator. You will be given a set of instructions to follow to reach a certain goal in the app. You have to generate Appium code based on the elements you find on the screen while navigating through the app.
-When asked to open buy SRP, use deeplink to open https://housing.com/in/buy/mumbai/<locality name>. For example: if asked to open 'Mira Road East' buy SRP, then open this deeplink: https://housing.com/in/buy/mumbai/mira_road_east
-Homepage deeplink -> https://housing.com/in/buy/real-estate-mumbai
-Only use the locator data from the Google Sheet at the end while generating test cases, don't use to navigate through screens, always get current screen elements and navigate then at end use locator data to generate code, if xpath is already present in sheet then directly add xpath locatorName to code if not then add the required xpath in comments which will then be added to the sheet manually
-Project dedicated page deeplink -> https://housing.com/in/buy/projects/page/16192-lotus-sky-garden-by-a-m-construction-and-lotus-group-in-malad-west
-Filters on the filter screen may initially be offscreen and require scrolling to view.
-Stop execution if any step fails.
-IMPORTANT: If the element you looking for is not present you can use swipe
-(Remember this properly - Very important) After the execution is successful/completed, do NOT analyze what you found or did; only generate Appium code.
-- waitForElementToBeVisible("locator_key", Wait.SHORT); locator_key is locator key and wait can be SHORT, MEDIUM, or LONG.
--  w3CGestures.scrollUp(n);  // n is the number of times to scroll. Up  and Down in scroll methods are direction of finger movement.
--  w3CGestures.scrollScreen("image_tour_navbar", ScrollDirection.MEDIUM_UP, 2); // image_tour_navbar is locator key, ScrollDirection can be SMALL_UP, MEDIUM_UP, LARGE_UP, SMALL_DOWN, MEDIUM_DOWN, LARGE_DOWN and 2 is max number of scrolls to perform, if not found in 2 scrolls then it will throw error. (DO NOT USE other methods except these two for scrolling)
-- navigateBack(); // for back action.
-- deepLink.OpenDeepLink("deeplink_key"); // deeplink_key is deeplink name.
-- getText("locator_key"); // to get text of element.
-- click("search_select", Wait.SHORT)
-- 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
-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
- */
+Use mobile-mcp.
+Navigate and explore the Housing app using the provided deeplink to validate, refine, and update the existing rough test scenarios.
+If the app cannot be navigated for a certain scenario (e.g., UI element not reachable, deeplink not loading, or navigation gets stuck), then generate the test cases based on the partial understanding achieved + standard expected Housing app behavior.
 
-@Test(priority = 19, dataProvider = "test-data", dataProviderClass = TestDataProvider.class)
-@Description("Test Description: Verify nearby properties functionality on new project dedicated page")
-public void npNearbyPropertiesVerification(HashMap<String, String> testData) {
-    detailPage.npNearbyPropertiesVerification(testData.get("np_dedicated_deeplink"));
-}
+Rewrite every rough test case into clean, modernized test cases using this structure:
 
 /**
- * Method Definition for DetailPage.java
- * Add this method to the DetailPage class
+ * TEST CASE <number>:
+ * * SUMMARY:
+ *   <Short high-level explanation of what is being validated>
+ * * SEVERITY:
+ *   <Low / Medium / High / Critical>
+ * * TEST DATA:
+ *   - Deeplink: https://housing.com/in/buy/projects/page/292551-treesourus-by-chandak-group-in-malad-west
+ * * TEST STEPS:
+ *   1. <step>
+ *   2. <step>
+ *   ...
+ * * EXPECTED RESULTS:
+ *   - <expected result 1>
+ *   - <expected result 2>
  */
 
-public void npNearbyPropertiesVerification(String deeplink) {
-    deepLink.OpenDeepLink(deeplink);
-    if (waitForElementToBePresent("later_btn", Wait.SHORT)) {
-        click("later_btn");
-    }
-    waitForElementToBeVisible("project_name", Wait.LONG);
-    waitForElementToBeVisible("Overview", Wait.SHORT);
-    w3CGestures.scrollScreen("high_value_project_title", ScrollDirection.MEDIUM_UP, 2);
-    waitForElementToBeVisible("high_value_project_title", Wait.SHORT);
-    String nearbyProjectsTitle = getElement("high_value_project_title").getText();
-    Assert.assertTrue(nearbyProjectsTitle.contains("Premium projects nearby"),
-        "Expected nearby projects section title to contain 'Premium projects nearby' but found: " + nearbyProjectsTitle);
-    w3CGestures.scrollScreen("near_by_project_name1", ScrollDirection.MEDIUM_UP, 2);
-    waitForElementToBeVisible("near_by_project_name1", Wait.SHORT);
-    waitForElementToBeVisible("near_by_project_price1", Wait.SHORT);
-    String expectedPropertyName = getElement("near_by_project_name1").getText();
-    String expectedPropertyPrice = getElement("near_by_project_price1").getText();
-    System.out.println("Expected Property Name: " + expectedPropertyName);
-    System.out.println("Expected Property Price: " + expectedPropertyPrice);
-    click("nearby_high_value_project1");
-    waitForElementToBeVisible("project_name", Wait.LONG);
-    waitForElementToBeVisible("project_price", Wait.SHORT);
-    String actualPropertyName = getElement("project_name").getText();
-    String actualPropertyPrice = getElement("project_price").getText();
-    System.out.println("Actual Property Name: " + actualPropertyName);
-    System.out.println("Actual Property Price: " + actualPropertyPrice);
-    Assert.assertEquals(actualPropertyName, expectedPropertyName,
-        "Property name mismatch. Expected: " + expectedPropertyName + " but found: " + actualPropertyName);
-    Assert.assertEquals(actualPropertyPrice, expectedPropertyPrice,
-        "Property price mismatch. Expected: " + expectedPropertyPrice + " but found: " + actualPropertyPrice);
-    waitForElementToBeVisible("Overview", Wait.SHORT);
-    waitForElementToBeVisible("Highlights", Wait.SHORT);
-    waitForElementToBeVisible("Property Tour", Wait.SHORT);
-    System.out.println("✓ Nearby properties verification completed successfully");
-    System.out.println("✓ Property '" + expectedPropertyName + "' opened correctly with matching price: " + expectedPropertyPrice);
-}
+Rules:
+- Clean up, merge, and modernize outdated or rough test cases.
+- Explore using mobile-mcp to verify flows and correct missing details.
+- Always specify the exact order of UI elements (icons, tabs, instant links, buttons).
+- When describing interactions, mention expected user-visible behavior (UI change, navigation, toggles, dialogs).
+- If navigation is not fully possible, infer expected behavior and generate the most accurate test cases.
+- Output only the test case blocks in the above format.
+- Final output must be suitable for aicode.txt.
+
+
+==========================
+EXAMPLE (follow EXACT style)
+==========================
 
 /**
- * Additional Locators to be added to the locator sheet or properties file:
- *
- * # Nearby Projects Section Locators
- * high_value_project_title=//android.widget.TextView[@text[contains(.,'Premium projects nearby')]]
- * high_value_project_section=//android.view.View[@content-desc='high_value_project_section']
- * near_by_project_name1=//android.widget.TextView[@content-desc='near_by_project_name1']
- * near_by_project_price1=//android.widget.TextView[@content-desc='near_by_project_price1']
- * near_by_project_name2=//android.widget.TextView[@content-desc='near_by_project_name2']
- * near_by_project_price2=//android.widget.TextView[@content-desc='near_by_project_price2']
- * near_by_project_name3=//android.widget.TextView[@content-desc='near_by_project_name3']
- * near_by_project_price3=//android.widget.TextView[@content-desc='near_by_project_price3']
- * near_by_project_name4=//android.widget.TextView[@content-desc='near_by_project_name4']
- * near_by_project_price4=//android.widget.TextView[@content-desc='near_by_project_price4']
- * nearby_high_value_project1=//android.view.View[@content-desc='nearby_high_value_project1']
- * nearby_high_value_project2=//android.view.View[@content-desc='nearby_high_value_project2']
- * nearby_high_value_project3=//android.view.View[@content-desc='nearby_high_value_project3']
- * nearby_high_value_project4=//android.view.View[@content-desc='nearby_high_value_project4']
- * project_name=//android.widget.TextView[@content-desc='project_name']
- * project_price=//android.widget.TextView[@content-desc='project_price']
- * project_address=//android.widget.TextView[@content-desc='project_address']
- * project_config=//android.widget.TextView[@content-desc='project_config']
- * later_btn=//android.widget.TextView[@text='Later']
- * Overview=//android.widget.TextView[@text='Overview']
- * Highlights=//android.widget.TextView[@text='Highlights']
- * Property Tour=//android.widget.TextView[@text='Property Tour']
- * Data Insights=//android.widget.TextView[@text='Data Insights']
+ * TEST CASE 1:
+ * * SUMMARY:
+ *   Validate visibility, order, and interaction behavior of header icons (Back, Share, Save/Shortlist, Chat) on the Project Detail Page.
+ * * SEVERITY:
+ *   High
+ * * TEST DATA:
+ *   - Deeplink: https://housing.com/in/buy/projects/page/292551-treesourus-by-chandak-group-in-malad-west
+ * * TEST STEPS:
+ *   1. Open the PDP using the provided deeplink.
+ *   2. Wait for the screen to load completely.
+ *   3. Verify the header displays icons in the following exact order (left to right):
+ *      - Back icon (far left)
+ *      - Project Name (center when applicable)
+ *      - Share icon
+ *      - Save/Shortlist icon
+ *      - Chat/Contact icon (if present in header or floating)
+ *   4. Validate that Share and Save/Shortlist icons appear adjacent to each other.
+ *   5. Tap the Share icon and verify that the system share sheet opens with available share targets.
+ *   6. Tap the Save/Shortlist icon and verify:
+ *      - Icon changes state (filled vs. unfilled)
+ *      - Property is added/removed from user’s shortlist
+ *   7. Locate the Chat/Contact icon and tap it.
+ *   8. Verify that interaction opens the expected contact flow (Developer chat screen, call options, or lead form).
+ * * EXPECTED RESULTS:
+ *   - Header icons appear in the correct order as per Housing app UI patterns.
+ *   - Share opens device share options without delay.
+ *   - Save/Shortlist toggles between saved/unsaved state with visual feedback.
+ *   - Chat/Contact opens the correct communication interface.
+ */
 
-** END OF SAMPLE FILE **
 ******** END OF GUIDELINES ********

package/lib/server.js

@@ -215,6 +215,33 @@ const createMcpServer = () => {
    }
  );
 
+ tool(
+   "mobile_learn_testcases_context",
+   "Reads previously saved app context notes and returns them so they can be used to validate or update test cases. This should be executed before generating manual test cases.",
+   {},
+   async () => {
+     try {
+       // Read app context notes from file
+       const notesFilePath = path.join(__dirname, "app_context.txt");
+       const fileContent = await fs.readFile(notesFilePath, "utf-8");
+
+       const notes = fileContent
+         .split("\n")
+         .map(line => line.trim())
+         .filter(line => line.length > 0);
+
+       if (notes.length === 0) {
+         return "No app context notes found.";
+       }
+
+       return `App context loaded for testcase generation: ${JSON.stringify({ notes })}`;
+     } catch (error) {
+       return `Error reading app context notes: ${error.message}`;
+     }
+   }
+ );
+
+
  tool("mobile_list_elements_on_screennn", "List elements on screen and their coordinates, with display text or accessibility label. Returns the complete XML structure to maintain hierarchy for XPath creation. Do not cache this result.", {}, async ({}) => {
      requireRobot();
      const xmlStructure = await robot.getElementsOnScreen();

package/package.json

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