Crawler Runs
Overview
The Crawler discovers real messages on your integration platform (SAP Cloud Integration or SAP PI/PO) over a chosen time window and turns them into test cases automatically. Every time a crawler configuration is started — by hand or on a schedule — it records a run.
A run is the bulk authoring step in action: in one pass the robot searches the platform for historical messages that match the configuration's criteria, then creates a test case from each suitable message and files it into the target folder. This page is where you confirm that the pass did what you expected — how much traffic was found in the window, how much of it became test cases, and how much was set aside. Reviewing runs is how you build confidence in a configuration before you let it run on a schedule and grow a regression suite on its own.
This page is the history of those runs. It shows one row per crawl, newest first, so you can see at a glance which crawls succeeded, how many messages each one found, and how many test cases were created or skipped. It is a read-only overview: you cannot start, edit, or delete crawls from here. To open the full picture of a single crawl — including per-interface results and the live or recorded log — open the run detail (see Related features).
A run carries a status that moves through Pending, Running, and then ends in Completed or Failed. Runs that were started in test run mode are flagged separately: those crawls only simulate the work and report the counts they would have produced, without actually creating any test cases.
Tasks
How to find a specific run
- Type part of a configuration name into the search box (Search by config name...). The list narrows as you type.
- Use the status drop-down to show only runs in a particular state (for example, only failed runs).
- Use the platform drop-down to show only runs against SAP Cloud Integration or only SAP PI/PO.
- To clear everything at once, select Clear filters.
How to open a run's details
- Find the run in the list.
- Select the configuration name in the Configuration column. It opens the detail view for that run, where you can review per-interface results and the run log.
How to export the run history
- Apply any filters you want — the export uses the rows currently shown.
- Select the export button at the top right of the list and choose your format (Excel or PDF).
Field reference
Each row summarises one crawler run. The figures are totals rolled up from every interface the crawl covered.
| Column | Description |
|---|---|
| Configuration | The crawler configuration that was run. Select it to open the run's details. |
| Platform | The integration platform the crawl targeted — SAP Cloud Integration or SAP PI/PO. |
| Status | Where the run is in its lifecycle: Pending (queued), Running (in progress), Completed (finished with no failures), or Failed (at least one interface errored). |
| Test Run | Whether the run was a test run (a preview that reports counts without creating test cases). |
| Messages | How many messages the crawl found on the platform within the chosen time window. |
| Created | How many test cases the run created. Always zero for a test run. |
| Skipped | How many discovered messages did not become test cases — typically duplicates, or messages dropped because the folder limit was reached. |
| Errors | How many errors occurred. Any value above zero means the run is marked Failed. |
| Started | When the run started. |
| Completed | When the run finished. Blank while a run is still pending or running. |
Tips & edge cases
- The list is read-only. You start, schedule, edit, and delete crawls from the crawler configuration screens, not from here. This page only shows the resulting run history.
- Test runs never create test cases. A run flagged as a test run reports the messages and counts it would have produced, so its Created count is always zero. Use it to size a configuration before committing to a real crawl.
- Skipped vs. created. A high Skipped count is usually expected: it reflects duplicate filtering and the per-folder cap on test cases, not a problem with the crawl.
- Failed runs. A run is Failed whenever any interface it covered reported an error. Open the run's details to see which interface failed and why.
- Empty list. If the list comes back empty (No crawler runs found), there may simply be no runs yet — or you may lack permission to see crawler configurations (see below).
- A low Found count usually means the window came up empty. Because a crawl only reads historical messages the platform kept, a run that found few or no messages often points at the time window or at missing platform retention rather than a fault in the crawl itself — for SAP Cloud Integration, no messages found can mean tracing was not active on those iFlows during the period you searched.
Related features
- Crawler run details — the per-interface results and log for a single run (route
/testcases/crawler-runs/:id). - Crawler configurations — where crawls are defined, scheduled, and started.
Prerequisites & permissions
To view this page you need the Crawler: Read permission. Without it, the run list will be empty or unavailable. Runs are further limited by project scope, so you only see runs for configurations within scopes you can access.
About permissions. Int4 Suite controls what you can see and do through roles and permission groups assigned to your user. Each role grants permissions on a specific resource (for example, Test Case, Automation Object, System Under Test) at one of four levels: Read, Write, Delete, or Execute. Some permissions are further narrowed by project scope, so you may have access to one part of the system but not another.
If a button is disabled or a list comes back empty, missing permissions are the most likely cause. Ask an administrator to review your role assignments, or check IAM → Users if you have the User: Read permission.
` and
``. The doc-user skill will ask before overwriting any marked region whose surrounding code has changed. -->