From fe5b2813acae27a239d18d1a362842822e4d4d43 Mon Sep 17 00:00:00 2001 From: Ravi Sawlani Date: Thu, 19 Oct 2023 19:00:13 +0530 Subject: [PATCH] Update the description of abortOnFailure for waitForElementVisible.js (#3934) --- lib/api/element-commands/waitForElementVisible.js | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/api/element-commands/waitForElementVisible.js b/lib/api/element-commands/waitForElementVisible.js index 28b0a9cdbd..325c5d787d 100644 --- a/lib/api/element-commands/waitForElementVisible.js +++ b/lib/api/element-commands/waitForElementVisible.js @@ -3,7 +3,7 @@ const WaitForDisplayed = require('./_waitForDisplayed.js'); /** * Waits a given time in milliseconds (default 5000ms) for an element to be visible in the page before performing any other commands or assertions. * - * If the element fails to be present and visible in the specified amount of time, the test fails. You can change this by setting `abortOnFailure` to `false`. + * If the element fails to be present and visible in the specified amount of time, the test will be marked as failed, and ordinarily, the subsequent steps/commands within the test-case/section will not be performed. However, you have the option to prevent the remaining steps/commands from being skipped by setting `abortOnFailure` to `false`. * * You can change the polling interval by defining a `waitForConditionPollInterval` property (in milliseconds) in as a global property in your `nightwatch.json` or in your external globals file. *