Use Chrome Developer Tools for AIQ Troubleshooting
Use Chrome Developer Tools for AIQ Troubleshooting
Use Chrome Developer Tools to inspect application behavior during troubleshooting, but rely on AIQ execution output and logs for repeatable test evidence.
Recommended guidance
- Use DevTools for local diagnosis of network, console, DOM, and performance symptoms.
- Do not require manual DevTools steps for automated Scenario Editor execution.
- Avoid capturing secrets, tokens, or personal data from network traces.
- Translate findings into stable locators, waits, validations, or environment fixes.
Validation workflow
- Reproduce the issue in a controlled browser session.
- Inspect console, network, DOM, or performance signals as needed.
- Update the AIQ scenario or environment based on confirmed findings.
- Validate the fix with a fresh AIQ execution.
Last updated: September 20, 2026