Creating an AMP Crawler

  • Updated

Overview

AMP allows users to create automated tests that spider a domain from a specified Start URL and test all pages encountered by the spider. When automated testing is performed in this manner, the results are saved to an AMP report that is created when the test is run. Automated tests can be run on demand or scheduled to run on a regular schedule.

Setting Up an AMP Spider

Tests are created for the asset that should be tested. On the Asset Dashboard, select the Tests link in the Asset Navigation widget. 

Asset Tests Location

On the subsequent page, select the "Create New Test" link, which opens up the test creation wizard.  

Test Configuration

Test Configuration form

AMP allows you to create an automated test in two ways: 

  1. Classic: Setup a start URL for the spider to start on
  2. CSV Upload: Upload a CSV with URLs to be tested by Access Engine

Classic Test

When setting up a classic test the following configurations should be set: 

  1. Test Name: Setup a name for the test. The date on which the test is run will be concatenated to the test name to create the name of the report that will be created to store the test results. 
  2. Report Owner: Select the user who should be set as the owner for the reports created by the test.
  3. Start URL: The page on which the spider should start.
  4. Viewport Size: Select the viewport size that should be used to test the site. The default is 1024 x 768, but users may select different viewport sizes to test accessibility of a responsive site as it would be viewed on different devices.
  5. Max Page Count: Select the maximum number of pages that should be scanned and tested. The default selection is 10 pages. 
  6. Publish Document Inventory: Select this checkbox if files should be published to the Document Inventory for future testing. 

CSV Upload

When setting up a CSV Upload test, the following configurations should be set: 

  1. CSV Spider Options: A single test can be setup to test all pages in the CSV file, or a separate test can be created for each URL in the CSV file.
  2. Test Name: Setup a name for the test. The date on which the test is run will be concatenated to the test name to create the name of the report that will be created to store the test results. 
  3. Report Owner: Select the user who should be set as the owner for the reports created by the test.
  4. Max Page Count: Select the maximum number of pages that should be spidered and tested. The default selection is 10 pages. 
  5. Publish Document Inventory: Select this checkbox if files should be published to the Document Inventory for future testing. 
  6. Document: Select the CSV file that contains the URLs to be tested.
  7. Viewport Size: Select the viewport size that should be used to test the site. The default is 1024 x 768, but users may select different viewport sizes to test accessibility of a responsive site as it would be viewed on different devices.

Optional Configurations

A number of optional settings can also be configured for both test types: 

  1. Test Scheduling: These optional settings allow you to set the test up to run on a predefined schedule. 
  2. Select Macros: Pre-recorded macros can be selected to be run on their related pages when encountered by the spider. 
    1. Both Assistant Macros or Selenium Scripts can be tied to a CSV Spider. You will be able to do this by tying the macro to the "Classic Configuration" first then switching to a "CSV configuration" and finishing up the setup. This will allow AMP to run the Macro first then start spidering the pages specified in the CSV. 
  3. Advanced Test Configuration: A number of optional configurations are available here, including the maximum page depth, negative and positive filters, iframe testing settings, and XPath exclusions. 

IFrame Testing Configurations

AMP Crawlers will automatically test the contents of iframes included on pages within the scanned asset. Level Access recommends this to all customers, because organizations are responsible for the accessibility of all content on their digital assets, whether created and hosted by them or not. However, customers may choose to ignore iframe contents in their automated testing by using one or more of the iframe testing settings in the Advanced Test Configuration sections of the crawler configuration. 

  • Ignoring All Iframe Contents: When the "Ignore Iframes" checkbox is selected, the contents of any iframe on any page will not be tested. Note that the iframe itself will be tested, but the page(s) within it will not. 
  • Apply Scope to Iframes: In some cases, organizations may only want to test the contents of iframes if those contents were created by and hosted by the organization. The Apply Scope to Iframes setting will force the crawler to respect the "Scope" settings, also in the Advanced Test  Configuration section. Use the Scope settings to specify what parts of the domain URL are indicative of the scope of the asset. To limit testing of iframe contents to those pages that are hosted within the asset's domain, make sure to also select the Domain Restriction option in the Scope field, in addition to selecting "Apply Scope to Iframes."

Was this article helpful?

2 out of 3 found this helpful

Have more questions? Submit a request