According to the docs, the `Is test` property "indicates whether the job is a test job".
This seems to only be the case when running jobs in Test Mode, not when running Test Cases.
Is this the intended functionality of this property, or is this a bug? If this is intended, the property name and description should really be updated...
Test Case Job Run (`Is test` is false):
Test Mode Job Run (`Is test` is true):
Hi @brettsherwood ,
In Workato, there’s an important distinction between a test case job, regular run(start the recipe) and a test job, which you can identify in the job report using the is_test property:
Test job: Triggered when you manually test a recipe. Here, Workato forces the trigger to run immediately, regardless of whether the actual trigger event has occurred. This is typically used to validate the recipe logic during development.
Regular job (is_test_job = false): Occurs when you start the recipe and wait for the real trigger event to happen. These represent actual production or scheduled runs, not simulated ones.
- Test case job(is_test_job = false): Executed as part of a structured test case suite (Select the trigger from the prior job reports)
In short,
Test job = forced run for validation.
Regular job = natural run from real-world trigger events.
Test Case Job= used to run a test scenario with mocked inputs for the trigger, allowing validation of the workflow without relying on real-time data.
This is not a bug; it's intentionally designed to differentiate between three types of runs: Regular, Test Case, and Test. Each type serves a distinct purpose in the workflow.
