Skip to main content

dynamic-content Scenario 1 — Wait for Angular App Render

Written by RTILA X Engineering Team

Beginner ~4 min

What You'll Learn

Wait for page load states before interacting

Real-World Use Case

Handling slow-loading sites

LIVE DEMO

Loading Angular app...
EXPECTED OUTPUT

RTILA X PROJECT JSON 

    {
  "name": "Wait_For_Angular_Render",
  "settings": {
    "urls": [
      "https://learn.rtila.com/scenarios/dynamic-content/1"
    ],
    "headless": false,
    "navigation_timeout": 30000,
    "max_concurrent_workers": 1,
    "humanoidEnabled": true,
    "humanoidSensitivity": "medium"
  },
  "datasets": {
    "ng_data": {
      "item_selector": "css=table.ng-data-table tr",
      "properties": [
        {
          "name": "row",
          "type": "text",
          "selector": "css=self"
        }
      ]
    }
  },
  "commands": [
    {
      "command": "goto",
      "params": {
        "url": "https://learn.rtila.com/scenarios/dynamic-content/1"
      }
    },
    {
      "command": "wait_for_selector",
      "params": {
        "selector": "css=#app-root .ng-content",
        "timeout": 30000
      }
    },
    {
      "command": "extract_data",
      "params": {
        "dataset": "ng_data"
      }
    }
  ]
}

SPAs like Angular often render content after a delay. The wait_for_selector command with a custom timeout pauses extraction until the app content is present in the DOM.

Did you complete this scenario?

Ready to run this automation?

Copy the project JSON above, open RTILA X, create a new project, and paste it.

Download RTILA X Free → View setup guide →

This scenario covers 1 RTILA X command and is referenced in 1 learning article.

Continue Learning

Was this helpful?