Skip to content

error handling doc fix #2083

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 15, 2025
Merged

error handling doc fix #2083

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
130 changes: 100 additions & 30 deletions docs/error-handling-kaneai.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,9 +9,9 @@ keywords:
- Testing
- Manual
- Accessibility Testing Settings
url: https://www.lambdatest.com/support/docs/error-handline-kaneai/
url: https://www.lambdatest.com/support/docs/error-handling-kaneai/
site_name: LambdaTest
slug: error-handline-kaneai/
slug: error-handling-kaneai/
---

import CodeBlock from '@theme/CodeBlock';
Expand Down Expand Up @@ -50,18 +50,104 @@ Use this guide to quickly identify, understand, and correct authoring issues to

## Error Categories for Web and App Authoring

| Category | Description | Common Authoring Error | Suggested Ways |
|-----------------------|--------------------------------------------------------------------|------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|
| Unsupported Operation | The command is not recognized or not supported. | Draw signature | Use only supported web actions, e.g., click, hover, type. |
| Invalid Parameter | The value provided is not valid for this command. | Switch to tab with index 0. | Use: scroll up, scroll down, scroll left, or scroll right. You can also use pixel value and percentage, scroll until. |
| Nested Conditional | Conditional logic inside another conditional is not allowed. | If X is visible then if Y is not visible then click it | Use separate, simple conditions. E.g., If X is visible then click it. |
| Missing Context | The system cannot determine the required state or context. | After clicking login, verify 'redirect happens' | Assert only on current, observable states. |
| Ambiguous Relationship| The property or relationship is too vague for the system to check.| 1- Check page loaded properly without errors; 2- Assert if input field is editable. | Use specific, testable properties (e.g., visible, enabled, disabled). |
| Invalid Assertion | The assertion is not valid or too broad. | 1-Assert all products are visible; 2-Check all products have price. | Assert each product individually or specify a count. |
| Excessive Queries | Too many elements are checked in one instruction. | Assert login, signup, user, password, continue, email is visible | Split into multiple instructions. |
| Too Complex | The instruction is too complex to process at once. | Assert user is logged in and profile is updated and dashboard is loaded | Break into smaller steps. |
| Unspecified Element | The element to interact with is not clear. | Click it, Type in input field | Specify the exact element, e.g., click 'Submit'. |
| Vague Instruction | The instruction is too unclear or incomplete. | Waiting, qwertyu, Perform login on this page. | Provide a specific action or check. |
### Unsupported Operation
**Description:** This command is not supported while authoring test cases. It applies to actions that cannot be executed in the authoring environment. <br />
**Common Authoring Error:** Draw signature or Take a screenshot, Hover over the settings icon <br />
**Suggested Ways:** Use supported web actions e.g., Use tap or click instead of hover or Try performing using slash commands in the prompt box.

---

### Invalid Parameter
**Description:** The value provided is not valid for this command. The value provided is not valid for this command. This may happen if the input is missing, outside the supported range, or formatted incorrectly.<br />
**Common Authoring Error:** Switch to tab with index 0 or Swipe top left. <br />
**Suggested Ways:** Use: scroll up, scroll down, scroll left, or scroll right. You can also use pixel value and percentage, scroll until.

---

### Nested Conditional
**Description:** Conditional logic cannot be placed inside another conditional. To avoid errors, break down the flow into separate, standalone conditions instead of nesting them. <br />
**Common Authoring Error:** If X is visible then if Y is not visible then click it.
**Suggested Ways:** Use separate, simple conditions. E.g., If X is visible then click it.

---

### Missing Context
**Description:** The system cannot determine the required state or context. This usually occurs when the instruction relies on information that hasn’t been defined, provided, or established earlier in the test. <br />
**Common Authoring Error:** After clicking login, verify 'redirect happens' or Verify the checkbox you ticked earlier is now unchecked.
**Suggested Ways:** Assert only on current, observable states.

---

### Ambiguous Relationship
**Description:** The specified property or relationship is too vague for the system to validate. Use clear and precise terms to ensure accurate validation. <br />
**Common Authoring Error:**

1. Check page loaded properly without errors
2. Assert if input field is editable

**Suggested Ways:** Use specific, testable properties (e.g., visible, enabled, disabled).

---

### Invalid Assertion
**Description:** The assertion provided is either not supported or is too broad to be validated. Use only allowed assertion operators and ensure the condition is specific and measurable. <br />
**Common Authoring Error:**

1. Assert all products are visible
2. Check all products have price

**Suggested Ways:** Assert each product individually or specify a count.

---

### Excessive Queries
**Description:** The instruction attempts to check too many elements at once. Reduce the number of queries to stay within the supported limit. <br />
**Common Authoring Error:** Assert login, signup, user, password, continue, email is visible
**Suggested Ways:** Split into multiple instructions.

---

### Instruction is Too Complex
**Description:** The instruction contains too many actions or conditions to be processed at once. Simplify it by breaking it into smaller, more manageable steps. <br />
**Common Authoring Error:** Assert user is logged in and profile is updated and dashboard is loaded
**Suggested Ways:** Break into smaller steps.

---

### Unspecified Element
**Description:** The target element is not clearly defined. Provide a specific identifier to ensure the system can locate the correct element. <br />
**Common Authoring Error:** Click it, Type in input field or Tap it.<br />
**Suggested Ways:** Specify the exact element, e.g., click 'Submit'.

---

### Vague Instruction
**Description:** The instruction is unclear or incomplete.
**Common Authoring Error:** Waiting, qwertyu, Perform login on this page.
**Suggested Ways:** Provide a specific action or check.

---

### Attribute Not Allowed
**Description:** Attribute used is not supported (e.g., button has color #333 on mobile). <br />
**Common Authoring Error:** Using blocked or unsupported attributes. <br />
**Suggested Ways:** Remove it or use a supported attribute.

---

### Invalid Variable Syntax
**Description:** The variable is written in an incorrect format, such as using extra or mismatched braces, spaces.
**Common Authoring Error:** Wrong variable like ``${{name}}`` or ``${ user }``.
**Suggested Ways:** Always use ``${var}`` or ``{{var}}`` format.

---

### Time Sensitive Assertion
**Description:** The instruction attempts to validate temporary UI elements such as toasts, spinners, or banners. These elements are short-lived and may lead to unreliable results; use stable post-conditions instead. <br />
**Common Authoring Error:** Example — assert toast says "Forecast job deleted". <br />
**Suggested Ways:** Instead, check something stable (e.g., row is gone, job is absent).

---

### Captcha Blocked

Expand Down Expand Up @@ -120,19 +206,3 @@ Use this guide to quickly identify, understand, and correct authoring issues to

<br />
> _Have any feedback or request? Reach out to us via support@lambdatest.com and we would be happy to hear from you._

| Category | Description | Common Authoring Error | Suggested Instruction |
|-----------------------|---------------------------------------------------------------------------|------------------------------------------------------------------|-----------------------------------------------------------------------------------|
| Unsupported Operation | The command is not recognized or not supported by the app or OS. | Hover over the settings icon | Use tap or click instead of hover. |
| Invalid Parameter | The value provided is not valid for this command. | 1- Swipe top left. 2- Type into search box. | 1- Give concrete instruction, e.g., up, down, left, right. 2- Type "Mobile" in search box. |
| Nested Conditional | Conditional logic inside another conditional is not allowed. | If X is visible then if Y is not visible then tap it | Use separate, simple conditions. |
| Missing Context | The system cannot determine the required state or context. | Verify the checkbox you ticked earlier is now unchecked | Assert only on current, observable states. |
| Ambiguous Relationship| The property or relationship is too vague for the system to check. | Ensure app is working | Use specific, testable properties (e.g., app is open). |
| Invalid Assertion | The assertion is not valid or too broad. | Assert all notifications are dismissed | Assert each notification individually or specify a count. |
| Excessive Queries | Too many elements are checked in one instruction. | Check if the first 5 checkboxes are visible | Split into multiple instructions. |
| Too Complex | The instruction is too complex to process at once. | Assert user is logged in and notifications are visible and settings are enabled | Break into smaller steps. |
| Unspecified Element | The element to interact with is not clear. | Tap it | Specify the exact element, e.g., tap 'Login'. |
| Vague Instruction | The instruction is too unclear or incomplete. | Perform login | Provide a specific action or check. |


> _Have any feedback or request? Reach out to us via support@lambdatest.com and we would be happy to hear from you._
Loading