Last week we announced that we would be doing a Feature Spotlight series to help you better understand the services provided by Testomato.
Our second post in the series will explain the different test settings you can choose from when customizing your Basic Testomato Test Suite, or any new tests that you wish to add to your project suite. We’ll give you a brief overview of the test options and a short explanation of each setting.
Once you have your basic test suite, you may wish to further customize your tests. To configure a test, click on the test name and a box like the one below will appear on your screen:
Select the settings you want and then, click Save.
What are your options?
Testomato allows you to check page content for the following problems:
HTTP Status Codes
For those of you who don’t know, HTTP status codes are a set of standard response codes (e.g. 404, 501, etc.) that are given by the website servers to a browser. These codes tell the browser whether everything was processed successfully, if a problem occurs, or if it needs to perform further action (e.g. redirect to another page).
Users can easily choose to test a page from a list of the following common HTTP status response codes:
- 200 OK
- 303 See Other
- 307 Temporary Redirect
- 403 Forbidden
- 404 Not Found
- 405 Method Not Allowed
- 500 Internal Server Error
- 501 Implemented
Looking for a different response code? Not to worry: you can also test for a specific code by selecting the option Other and manually entering in the code you wish to test.
(NOTE: Testomato cannot currently check 301 and 302 responses correctly, but we’re working hard to fix this problem.)
Common Error Messages
Error messages are displayed when an unexpected condition occurs on your website. Unlike HTTP status codes, which describe the status of an entire webpage, error messages could describe anything from coding to server errors and can occur anywhere on a website directly within the HTML code.
Testomato currently checks for these common error messages:
- Common server error messages
- All types of PHP error messages
- All MySQL error messages
- XDebug output
- Nette debug output (common in Czech Republic)
- Database connection errors
When configuring test settings, users also have the option to test for a specific text string or a missing text string. A text string simply means a piece of text (e.g. iPhone) that appears on a page. You can configure your test to check for a specific text string or to ensure that a piece of text you do not want/should not be there is present (i.e. test for typos like “Aple” on your web page). These tests are case sensitive, so make sure you PaY ClosE AtTentioN to the text you enter!
See an example of a text string configuration below:
You can test more than one string in a test – simply write each test string on a separate line.
It’s also possible to test the HTML content on a page. For example, you can easily check if the correct h1 heading is present by writing “<h1>Your Cool Title</h1>” in the text box.