Selenium waits for browser navigation or a specific page condition; CogniRunner governs Jira workflow behavior. Selenium helps a test avoid issuing its next browser command before the page or UI is ready. CogniRunner can determine whether Jira offers a transition, validate an attempted transition, or run an action after that transition commits. They solve different problems and are not substitutes.
What each product is controlling
Selenium controls a WebDriver session interacting with a browser. Its waits synchronize test commands with navigation readiness or with a condition the test chooses to poll. The central question is: “Is the browser or the specific UI state ready for the next command?”
CogniRunner is a Jira Cloud workflow and automation app. Its transition rules operate on Jira issues and workflow lifecycle events. The central question is: “Should Jira offer or permit this transition, and what should happen after it commits?” The Marketplace also lists event listeners and cron-scheduled jobs, which can run outside a transition flow.
That difference matters: waiting for a field to appear in a browser is not the same as deciding whether an issue may move to another Jira status.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →#1 Best Overall
How Selenium waits handle browser timing
Navigation readiness is not application readiness
Selenium navigation commands wait according to the session’s page-load strategy. The default normal strategy targets document.readyState value complete; eager targets interactive; and none does not wait for a readiness state. These options describe browser document readiness, not whether every JavaScript-driven part of an application has finished rendering. A single-page app may continue changing after the document reaches complete, so that state alone does not prove the element a test needs is ready. Selenium also notes that navigation triggered by a click or form submission is not covered in the same way as URL navigation. See Selenium’s browser options documentation and the W3C WebDriver specification.
Implicit waits apply to element searches globally
An implicit wait is a session-wide setting for element-location calls. Its documented default is zero. If set to a nonzero duration, a failed element lookup can keep searching until the element appears or the interval expires. This can be useful when elements commonly take a short time to enter the DOM, but it applies broadly rather than to one specific application condition.
Rank #2
Explicit waits poll a chosen condition
An explicit wait is attached to a particular condition, such as an element becoming visible. Selenium polls that condition until it succeeds or the timeout expires; polling interval, ignored exceptions, timeout, and timeout message can be customized. For a button that reveals a field, an explicit wait for that field to become visible is more directly targeted than assuming navigation completion means the field is ready. Selenium warns against mixing implicit and explicit waits because their combined timing can be unpredictable. Details are in Selenium’s waiting strategies documentation.
How CogniRunner handles Jira workflow transitions
Conditions determine whether a transition is offered
A CogniRunner condition affects whether Jira presents a workflow transition as available. It is appropriate when a transition should not be offered until a stated condition is met. LeanZero describes its conditions as deterministic checks evaluated by Jira.
Validators check an attempted transition
A validator runs when someone attempts the transition. If validation returns a negative verdict, CogniRunner can block the transition and show an explanation. This is a workflow enforcement point, not a browser wait: it evaluates whether the Jira issue may advance rather than whether a browser element has appeared.
There is an important operational qualification. LeanZero documents fail-open handling for validator failures: only a completed negative validation verdict blocks, while infrastructure failures and certain unavailable configurations allow the transition. This is CogniRunner-specific behavior, not a general Jira guarantee. Check the active app version and rule configuration before relying on a validator as a hard control. See LeanZero’s CogniRunner documentation.
Post-functions run after the transition
A post-function acts after a transition commits. Use it for work that belongs after the issue has moved, rather than for hiding a transition in advance or rejecting an attempted one.
Listeners and scheduled jobs can run outside transitions
The Atlassian Marketplace listing also describes Jira event listeners and cron jobs scoped over JQL. Those mechanisms are separate from transition conditions, validators, and post-functions; their trigger can be an event or schedule rather than a user attempting a workflow transition. The listing identifies CogniRunner as a Jira Cloud app: Atlassian Marketplace listing.
Recommended Free Tools
Side-by-side: timing, triggers, and outcomes
| Question | Selenium | CogniRunner |
|---|---|---|
| Primary system | Browser and WebDriver session | Jira Cloud workflow and automation |
| What starts the behavior? | Navigation command, element lookup, or explicit-wait call | Transition offer or attempt, post-transition hook, Jira event, or schedule |
| What is evaluated? | Document readiness or a polled browser/application condition | Whether a transition is offered or permitted, or what action follows it |
| Where does it apply? | Page-load strategy is session-level; implicit wait applies globally to element searches; explicit wait targets a chosen condition | Rules attach to workflow transitions, events, or scheduled jobs |
| What happens on completion or failure? | A condition succeeds or times out; an element lookup may wait for its implicit-wait interval | A validator may pass or block; a condition may hide a transition; a post-function acts after commit; documented validator failure paths can fail open |
| Key caution | readyState does not guarantee application readiness; mixing implicit and explicit waits can make timing unpredictable |
A workflow validator is not browser synchronization, and fail-open behavior affects enforcement assumptions |
Choose the mechanism that matches the problem
- Use a Selenium navigation strategy to set how a WebDriver navigation command waits for document readiness.
- Use a Selenium explicit wait when the next browser action depends on a specific element or UI condition becoming true.
- Use a CogniRunner condition when a Jira transition should be hidden unless a condition is met.
- Use a CogniRunner validator when an attempted transition must be checked and may need to be blocked.
- Use a CogniRunner post-function when an action belongs after the transition commits.
- Consider a listener or cron job when the automation should run from a Jira event or schedule rather than from a transition.
Version and scope to check before implementation
Atlassian Marketplace showed CogniRunner version 6.1.0 for Jira Cloud, released October 3, 2026, when checked October 4, 2026. Listing details can change, so verify the current Marketplace entry before relying on version-specific information. Selenium’s documentation describes WebDriver behavior but does not specify one binding version for every implementation. Check the Selenium binding, browser and driver, Jira deployment, CogniRunner version, and active rule configuration relevant to your environment.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
