An HTML Code Test examines HTML Code that you input directly into the test configuration, rather than retrieving HTML from a web server. This allows you to see how your code performs in a test environment before running it live on your website.
HTML Code Test Properties | |
|---|---|
| Name | A name used to identify this test. |
| Description | Optional additional information about the test |
| Monitor |
|
| Test HTML | The HTML code being examined. You can enter any code supported by an HTML browser. Catchpoint does not perform any kind of validation on the code and will test it exactly as it is entered in this field. (see example code below.) |
| Location | The Product/Folder location of this test (read only) |
| Status | Determines whether this test is current Active or Inactive |
Test HTML Code Structure:
<html>
<head>
</head>
<body>
{Code to be tested}
</body>
</html>
The maximum length allowed is 4000 Unicode characters. You can also use Macros to add variables to the code.
Supported Metrics |
|
|---|---|
| # Connections | The total number of TCP connections established during the test. |
| # Content Load Errors | The total number of elements on the webpage that the test was unable to load or that generated errors during loading. |
| # CSS | Total number of CSS files downloaded during the test. |
| # Flash | Total number of Flash files downloaded during the test. |
| # Font | Total number of font files downloaded during the test. |
| # Hosts | The total number of unique external hosts referenced by elements on the page. |
| # Html | Total number of HTML files downloaded during the test. |
| # Image | Total number of image files downloaded during the test. |
| # Items (Total) | The total number of files included on the webpage. For Object monitor tests, this value is always one. |
| # JS Errors per Page | The average number of JavaScript errors on each webpage. |
| # Media | Total number of media files downloaded during the test. |
| # Other | Total count of all files not defined otherwise. |
| # Purged Runs | The number of test runs manually excluded from calculation for purposes of SLA accuracy. |
| # Redirect | Total number of redirects on the webpage. |
| # Runs | Total number of test runs for the defined time period. |
| # Script | Total number of JS files downloaded during the test. |
| # Test Errors | The total number of elements that Catchpoint was unable to connect to, receive a response from, or load on the page. |
| # Test Failures | The total number of test runs that failed at the test URL level |
| # Tests with JS Errors | The number of individual test runs that resulted in at least one JavaScript error. |
| # Timeout Failures | The number of times a test failed because a server process did not complete and it returned a timeout. |
| # XML | Total number of XML files downloaded during the test. |
| # Zones | The number of defined Zones containing hosts that were accessed during the test. |
| % Adjusted Availability | Ignoring any purged runs, the percentage of test runs where the primary URL server was reached and the test was completed (i.e. there was not a Test Error.) |
| % Availability | The percentage of test runs where the primary URL server was reached and the test was completed (i.e. there was not a Test Error.) Availability is calculated as: (# Test Runs - # Test Errors) / # Test Runs |
| % Content Availability | The percentage of time that all the elements on the webpage were available. Content Availability is calculated as the number of times the test ran successfully with no loading errors, divided by the total number of times the test ran. If at least one object failed to load during testing, that test run is regarded as having content that failed to load properly. |
| % Downtime | The percentage of test runs where the primary URL server was unavailable, unreachable, or otherwise failed (i.e. there was a Test Error.) Downtime is calculated as: # Test Errors / # Test Runs |
| % Frustrated | The percentage of test runs that exceeded the Apdex “frustrated” threshold. |
| % Not Frustrated | The percentage of test runs that completed in less time than the Apdex “frustrated” threshold. This is equivalent to: % Satisfied + % Tolerating |
| % Satisfied | The percentage of test runs that completed in less time than the Apdex “Satisfied” threshold. |
| % Self Bottleneck | The percentage of Document Complete time that hosts in the "self" zone were a bottleneck for. |
| % Third Party Bottleneck | The percentage of Document Complete time that hosts in the "third party" zone were a bottleneck for. |
| % Tolerating | The percentage of test runs that exceeded the Apdex “Satisfied” threshold but completed in less time than the “Frustrated” threshold. |
| Apdex | A scoring mechanism that translates performance metrics of diverse applications into generic “User Satisfaction” levels using predefined response time thresholds. You can use default Apdex thresholds or configure your own on a per basis. For more details about Apdex, visit http://www.apdex.org/ |
| Client Time (ms) | The total amount of time where no request was on wire, from the start of the test or step to Document Complete. |
| Content Load (ms) | The time it took to load the entire content of the webpage after the connection was established with the primary URL server. This is the time from the end of Send (ms) until the final element, or object, on the page was loaded. |
| CSS Bytes | Total size of CSS files downloaded during the test, in bytes. |
| Document Complete (ms) | The time it took from the initial URL request being issued until the browser triggered the "onload" event. Any inline requests or requests inserted via "document.write" must complete loading before the event is fired. Document Complete does not account for dynamic requests that may be generated later via JavaScript and/or DOM manipulation. |
| DOM Load (ms) | The time it took to load the Document Object Model (DOM) for the webpage. |
| Downloaded Bytes | The total number of downloaded bytes from the primary URL of the test(s). |
| Experience Score | A composite metric that captures the overall experience of a user on a scale of 0-100. |
| First Contentful Paint | The time when the browser rendered the first bit of content from the DOM. (May be text, image, SVG, or even a <canvas> element.) |
| First Paint | The time when the browser first rendered anything visually different from what was on the screen prior to navigation. |
| Flash Bytes | Total size of Flash files downloaded during the test, in bytes. |
| Font Bytes | Total size of font files downloaded during the test, in bytes. |
| Frames Per Second | Measures the performance of animations. |
| Html Bytes | Total size of HTML files downloaded during the test, in bytes. |
| Image Bytes | Total size of image files downloaded during the test, in bytes. |
| Media Bytes | Total size of media files downloaded during the test, in bytes. |
| Other Bytes | Total size of all files not defined otherwise. |
| Render Start (ms) | The time from initial navigation until the first visual content is painted to the browser display. |
| Script (ms) | Total time spent loading JS files, in milliseconds. |
| Self Downloaded Bytes | Total file size in bytes (including headers) downloaded from hosts in the "self" zone. |
| Signal Quality | Measures the quality of the WLAN connection in terms of data transfer speed. It indicates what percent of the available network are you using to move data (upload / download). 99% is as good as it gets in terms of signal quality. |
| Signal Strength (dBm) | This number represents the power the clients device is receiving from the Access Point / Wi-Fi router. A number of -30 dBm indicates excellent while a number of -70dBm indicates very poor signal strength. |
| Test Time (ms) | One cohesive metric that applies to all test types and indicates the total duration of the test run. Test Time is equivalent to Response, Test Response (Transaction and web tests) and ping RTT (Trace Route tests), and is used when calculating Apdex. Test Time is not available for Request, Host, or Zone charting. |
| Time To Interactive | The time when the page first became interactive. TTI marks the point at which the webpage is both visually rendered and capable of reliably responding to user input. |
| Time to Title (ms) | The time from initial navigation until browser displayed the title of the page. |
| Visually Complete (ms) | The time when the visual area of a page has finished loading, meaning that all visible elements of the web page are 100% loaded. |
| Webpage | |
| Webpage Throughput | Measures how efficiently the system downloaded the content of the entire webpage. Webpage Throughput is calculated as: (File Size + Header Size) / Webpage Response (ms) |
| Wire Time (ms) | The total amount of time where at least one request was on the wire, from the start of the test or step to Document Complete. |
| XML Bytes | Total size of XML files downloaded during the test, in bytes. |