Search Results

AppvanceIQ performs vulnerability testing according to the OWASP Top Ten. For more information see OWASP Top Ten. "The OWASP Top Ten is a standard awareness document for developers and web application security. It r...

AIQ has support for ZAP (Zed Attack Proxy), which is a free, open-source penetration testing tool being maintained under the umbrella of the Open Web Application Security Project (OWASP). ZAP is designed specifically for testing web applications and is both fl...

Recommended guidance Application penetration testing content must stay within approved scope and customer authorization. Use AIQ and Scenario Editor terminology for current workflows, and avoid documenting steps that could be interpreted as bypassing security ...

Recommended guidance Use the Play Page to review and manage AIQ executions, recent runs, and result evidence. The page is useful for confirming whether a run started, completed, failed, or produced output that requires deeper troubleshooting. What to review Ex...

Use the Analyze Page The Analyze page helps review execution results and identify where a scenario, service, or performance run needs attention. Use it after a test completes, or while reviewing a run that produced unexpected behavior. What to review Overall p...

Use this article when AIQ needs to compare PDF output by text, structure, selected rules, metadata, page count, or approved binary comparison. What changed in this article Renamed and scoped this duplicate PDF comparison page as a compact reference. Aligned it...

Last reviewed: September 29, 2026 Use this article to understand when AIQ Auto Correlation should be used to detect and reuse dynamic values across requests or steps. What changed in this article Expanded the short title into an overview of what Auto Correlati...

Last reviewed: September 29, 2026 Use this article to understand the mechanics of AIQ Auto Correlation and how extracted values are applied during replay. What changed in this article Kept the “how it works” focus but added clearer mechanics around extraction,...

Recommended guidance Use Validation Suite and Store Content features when AIQ tests need to verify content, files, responses, or extracted values as part of repeatable validation. Keep validation assets organized so the expected evidence is clear and maintaina...

Validation and Store Content in Scenario Editor Use validation and stored content when a Scenario Editor test needs to capture a value from the application and compare it later in the same scenario or execution. This keeps the test focused on business behavior...

Last reviewed: September 25, 2026 Use this article when a test needs to capture, validate, or store HAR network content for later analysis. What changed in this article Updated the title to clarify that the page is about HAR content, not the whole Validation a...

The Store tab in the Scenario Editor allows you to define extractors that listen for a specific Step and Request and extract data from its response. When creating a Store or Assert entry in the Scenario Editor, you must configure the Target according to the ty...

Extract and Validate PDF Content Use PDF content extraction when a Scenario Editor test needs to confirm that a generated PDF contains expected text or values. This is most useful for invoices, statements, confirmations, reports, and other documents produced b...

Use this article when a scenario or service workflow needs to run an approved command-line script type in a controlled AIQ execution environment. What changed in this article Scoped command-line script execution as a controlled capability, not a generic shell-...

Recommended guidance Service Suite is AIQ’s API and service testing area for building HTTP requests, validating responses, extracting values, and supporting API-driven test workflows. Use “Service Suite” in current documentation instead of older Services Workb...