Error Handling in Authoring
This page provides a comprehensive reference for common errors encountered when authoring automated test cases for both web and app platforms. Each table below lists error categories, describes what they mean, gives examples of instructions that are not accepted, and suggests how to write correct instructions.
Use this guide to quickly identify, understand, and correct authoring issues to ensure your test cases run smoothly.
Error Categories for Web and App Authoring
Unsupported Operation
Description: This command is not supported while authoring test cases. It applies to actions that cannot be executed in the authoring environment.
Common Authoring Error: Draw signature or Take a screenshot, Hover over the settings icon
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.
Common Authoring Error: Switch to tab with index 0 or Swipe top left.
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.
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.
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.
Common Authoring Error:
- Check page loaded properly without errors
- 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.
Common Authoring Error:
- Assert all products are visible
- 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.
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.
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.
Common Authoring Error: Click it, Type in input field or Tap it.
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).
Common Authoring Error: Using blocked or unsupported attributes.
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.
Common Authoring Error: Example — assert toast says "Forecast job deleted".
Suggested Ways: Instead, check something stable (e.g., row is gone, job is absent).
Captcha Blocked
Description: If CAPTCHA is detected on screen, the test flow will be halted immediately, as interacting with CAPTCHA (e.g., solving puzzles, entering characters) is not supported.
Common Authoring Error: Selecting CAPTCHA checkbox or entering CAPTCHA text.
Suggested Ways: Generally, CAPTCHA is not present in application used for testing. If you encounter a CAPTCHA, try testing the application where CAPTCHA is disabled or not triggered.
Loop Detected
Description: The same operation is repeated 3 or more times without any state change, indicating a possible infinite loop.
Common Authoring Error: Repeating the same action (e.g., clicking) without checking state.
Suggested Ways: Review and update the flow to ensure that each iteration results in a state change to avoid loops.
Persistent Loader
Description: If a loading spinner or progress indicator stays visible for too long—specifically, after waiting multiple times or for more than 30 seconds—it usually means the system is stuck and not progressing as expected.
Common Authoring Error: Waiting forever for the loader to go away without handling timeouts.
Suggested Ways: Implement a timeout to stop waiting after a reasonable period. Use checks that confirm when the page or content has fully loaded instead of relying only on the loader disappearing.
Dead Click
Description: If you keep clicking the same element but nothing happens—no change on the screen, no popup, and no response—this means the click isn’t having any effect.
Common Authoring Error: Repeatedly clicking on an element that isn’t interactive or is disabled.
Suggested Ways: Make sure the element you want to click can actually be clicked and will trigger some action before clicking it. stop the flow if clicks don’t cause any response.
Navigation Stuck
Description: If you try to navigate multiple times but nothing changes on the screen, and the system can’t confirm that the navigation succeeded, it means the navigation is stuck.
Common Authoring Error: repeatedly navigating without checking if the page or state actually changed.
Suggested Ways: check the navigation to ensure it is successful and the page or state changes as expected.
Lambda Error
Description: This error indicates an internal issue within the system. it may be caused by problems such as creating input parameters, accessing secrets, or other internal issues.
Common Authoring Error: Errors related to parameter configuration, secret management, or system-level issues.
Suggested Ways: Please attempt to resolve the issue on your side. if the problem continues, contact support at support@lambdatest.com for assistance.
Reached Maximum Step Limit
Description: During the generative step, if the number of steps reaches the maximum limit of 50, this error occurs.
Common Authoring Error: Flows that are too long or contain loops causing excessive steps.
Suggested Ways: Simplify the flow by breaking it into smaller parts and ensure there are no infinite loops or unnecessary steps.
Have any feedback or request? Reach out to us via support@lambdatest.com and we would be happy to hear from you.
Chat with Us
Ask the Community