Create automated tests that scan a list of pages from your website. AMP saves the scan test reports to your asset. Run AMP tests on-demand for immediate results or set a recurring schedule and monitor your compliance over time.
Note that the list of pages is static and you may need to update it as your website URLs change. To reduce manual effort as your needs change, you can create AMP crawler tests instead.
On this page:
Create a test
To create a test:
- In AMP, select Assets.
- Find the asset you want to create the test for.
- Select the asset name.
- Under Asset Navigation, choose Tests.
- Select Create New Test.
Configure the test
To configure the test:
- Select CSV upload.
- If you haven't:
- Download the template for the CSV under Publish Document Inventory.
- Fill in the details.
- Save the file to your computer
- Choose Create a single test.
- Enter and select the test configuration requirements.
- Optionally, set up:
- Select Submit.
Test configuration details
Test configuration requirements
The table below describes the classic test configuration requirements.
Field | Description |
---|---|
Test Name | Enter the name of the test. Every time the test is run, it will auto-populate the date of the test to differentiate the test reports. |
Report Owner | Select the user you want to own the reports from this test. |
Max Page Count | Select the maximum number of pages to test. Default is 10 pages. |
Publish Document Inventory | Select this option if you want files published to the Document Inventory for future testing. |
Document | Upload your completed CSV file. This option is only available for CSV upload method. |
Viewport Size | Select the viewport size. Default viewport size is 1024x768 but you can change it to test the accessibility of responsive websites. |
Test scheduling (optional)
The table below describes the classic test scheduling options.
Field | Description |
---|---|
Date of first report | Select the date of the first test scan. |
Report start time | Select the time of the test scan. Each recurring scan will be run at this time. |
Recurrence | Select the recurrence. |
Advanced test configurations (optional)
The table below describes the advanced test configuration options.
Field | Description |
---|---|
Ignore Iframes | Ignore iframes and their violations during the test. |
Apply Scope To IFrames |
Only tests iframes if they're in scope. For example, if the scope is www.levelaccess.com, and the homepage includes one iframe from the website and one from the LinkedIn feed, this option only tests the iframe from the Level Access website. |
Ignore URL Fragments | Ignores URL fragments from link harvesting to reduce the number of URLs being tested. URL fragments specify a location within a page using #. |
Ignore Query String |
Ignores URL query strings during link harvesting to reduce the number of duplicate URLs. For example, the words you enter into a search bar on a webpage are in the URL as a query string. |
XPath Exclusions |
Excludes a common section of your website from testing. For example, a specific div element. Format your XPath exclusions like this: /html/body/div[@id="RandomAds"], and separate additional XPaths using commas. Note: the XPath Exclusion field supports full XPath Syntax. For example, the not() XPath expression, as in: //*[not(ancestor-or-self::main)] Use this flexibility to narrow in on the specific portion of the page you'd like to test in your spiders. |
User Agent | Test using a mobile user agent or Firefox. If you leave this field empty, AMP tests using Chrome. |
Scope |
The basic restriction on the type of pages you want to test. Path Restriction only tests pages that are present at or below the path of the Start Location. For example, if the Start Location is http://www.levelaccess.com/contact.php, you'll only test pages in the contact directory or its sub-directories on the www.levelaccess.com server. |
Comments
0 comments
Article is closed for comments.