fix: Fix for locator for AddWidgetTableAndBind_spec test case

[sagar-qa007]

Description

Found minor locator failure

Fixes # https://app.zenhub.com/workspaces/stability-pod-6690c4814e31602e25cab7fd/issues/gh/appsmithorg/appsmith/38314

Automation

/ok-to-test tags="@tag.Datasource,@tag.Sanity"

🔍 Cypress test results

Tip

🟢 🟢 🟢 All cypress tests have passed! 🎉 🎉 🎉
Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/12465389478
Commit: 9cf2fbe
Cypress dashboard.
Tags: @tag.Datasource,@tag.Sanity
Spec:

---

Mon, 23 Dec 2024 13:19:11 UTC

Communication

Should the DevRel and Marketing teams inform users about this change?

• Yes
• No

Summary by CodeRabbit

• Bug Fixes
  • Updated the locator for the query response to ensure accurate referencing of the second row in the table, improving the application's interaction with query results.

[coderabbitai]

Walkthrough

This pull request involves a minor modification to an XPath locator in the QueryEditor.json file within the Cypress test suite. The change adjusts the target row for a query response locator from the third row to the second row, which could impact how specific elements are selected during test automation.

Changes

File	Change Summary
app/client/cypress/locators/QueryEditor.json	Updated XPath selector for queryResponse from third row [3] to second row [2]

Suggested labels

Bug, ok-to-test, skip-changelog

Suggested reviewers

• ApekshaBhosale
• NandanAnantharamu

Possibly related PRs

• chore: Update selectors for Table Response #38302: Updates XPath expression for the queryResponse locator in the same QueryEditor.json file

Poem

Locators dance, rows shift and sway
XPath selectors find their way
From third to second, a subtle slide
Testing's precision, we can't hide! 🕵️‍♀️🔍

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[sagar-qa007]

/ci-test-limit-count run_count=3 update_snapshot=true specs_to_run=cypress/e2e/Regression/ServerSide/QueryPane/AddWidgetTableAndBind_spec.js

[github-actions]

Tests running at: https://github.com/appsmithorg/appsmith/actions/runs/12465401100.
Cypress dashboard
PR: #38313 with spec: cypress/e2e/Regression/ServerSide/QueryPane/AddWidgetTableAndBind_spec.js .

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between dcb27d2 and 9cf2fbe.

📒 Files selected for processing (1)

• app/client/cypress/locators/QueryEditor.json (1 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

app/client/cypress/locators/QueryEditor.json (1)

Pattern app/client/cypress/**/**.*: Review the following e2e test code written using the Cypress test library. Ensure that:

• Follow best practices for Cypress code and e2e automation.
• Avoid using cy.wait in code.
• Avoid using cy.pause in code.
• Avoid using agHelper.sleep().
• Use locator variables for locators and do not use plain strings.
• Use data-* attributes for selectors.
• Avoid Xpaths, Attributes and CSS path.
• Avoid selectors like .btn.submit or button[type=submit].
• Perform logins via API with LoginFromAPI.
• Perform logout via API with LogOutviaAPI.
• Perform signup via API with SignupFromAPI.
• Avoid using it.only.
• Avoid using after and aftereach in test cases.
• Use multiple assertions for expect statements.
• Avoid using strings for assertions.
• Do not use duplicate filenames even with different paths.
• Avoid using agHelper.Sleep, this.Sleep in any file in code.

[github-actions]

Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/12465401100.
Cypress dashboard: Click here!
The following are new failures, please fix them before merging the PR:
To know the list of identified flaky tests - Refer here

***** Repeat Run Summary ***** Total Tests with repeat: 9 Total Passed: 9 Total Failed: 0 Total Skipped: 0 *****************************