Welcome
Welcome to the documentation for HCL AppScan Standard version 10.4.0
Getting started
This section provides a short tour of basic product features and procedures, including using the wizard to set up a scan.
Configuration
You configure a scan by choosing settings that best describe your application, and the kind of testing you want.
Manual exploring
Manual exploring enables you to explore specific parts of your application, filling in fields and forms as you go. This can be a way of ensuring that particular areas of the site are covered, and that AppScan has the information needed to complete forms correctly.
Scanning
Learn how to start a scan, and what happens during the scan; how to manually manipulate the Explore stage, and how to export the results of a scan.
Data
Data view is populated with information about the structure of the site during the Explore stage of the scan.
Issues
Issues view provides access to the results of a scan. You can view results at a high level or select specific tests or objects and access more details. These details include how to fix, requests/responses, and differences between the test variants that resulted in issues. You can manipulate the severity of issues, resend tests (with or without modifications), and create reports based on Issues.
Reports
This section describes how to generate reports from the scan results.
Tools
This section explains how to use additional tools provided with HCL AppScan Standard.
Integrations
This section describes integrations of other applications with AppScan Standard:
- AppScan on Cloud
  This section describes ways AppScan Standard can interact with HCL AppScan on Cloud, to scan apps on the cloud.
- AppScan Enterprise
  This section describes ways AppScan Standard and Enterprise editions can interact.
- Automation Frameworks
  You can use scripts written for your QA automation framework (such as Selenium) to create Manual Explore recordings for an AppScan scan.
  - Creating the batch command
    This example offers general guidelines for running a scan using an automation framework script for the Explore stage.
Best practices
This section contains some best practices and use cases for advanced users.
FAQ & Troubleshooting
CLI
This section describes the syntax and options available using the Command line interface.
References
Menus and toolbar summaries, and glossary

Automation Frameworks

You can use scripts written for your QA automation framework (such as Selenium) to create Manual Explore recordings for an AppScan scan.

If your QA personnel use an automation framework to run functional tests on your web app, you can take advantage of the scripts that are already written to create tailor-made scans. The requests from the automation framework to the app are sent with AppScan as proxy, enabling AppScan to record the actions as an Explore stage for its own scan. AppScan then tests the site based on that Explore stage. This is done using the AppScan CLI.

In principle you create and run a batch command that does the following:

Open AppScan and configure:
1. Starting URL
2. User credentials
3. Test Only
4. Open AppScan's proxy with a specific listening port
Run the automation framework script through the same port.
When the script ends, close AppScan’s proxy and the Test stage starts.
Save the scan results, and optionally create and save a report.

The section following gives guidelines for testing any site with any automation framework.