Follow

Creating an AMP Test

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. 

Assets Tests

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

Test Configuration

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. Browser Emulation: Select the browser that should be used for testing. This setting will change the user agent used by the spider.
  5. Max Page Count: Select the maximum number of pages that should be spidered 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. Browser Emulation: Select the browser that should be used for testing. This setting will change the user agent used by the spider.

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. 
  3. Advanced Test Configuration: A number of optional configurations are available here, including the maximum page depth, negative and positive filters, and XPath exclusions. 
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

Level Access Support
www.levelaccess.com | 800.889.9659
© 2005 - 2018 - Level Access All rights reserved.
Privacy | Security | Credits | License