Developers and QA professionals use Assertible to write and automate tests for web services. The Dashboard is where you can create new tests, manage web services, and view detailed results for failing and passing tests.

Below are a few basic definitions that will be helpful when using Assertible and reading through the docs:

Web Services

A web service contains the required settings for making a request to an HTTP endpoint. For example, assertible.com could be a web service. This makes it easy to organize tests for known web services.

Tests

A test is a single request to an HTTP endpoint. You can run a test, make assertions on the response, and run it on a specified schedule, amongst other things.

Test Results

The result of a test and all of it's assertions. A test result will always be in a know state: Pending, Failing, Passing. Test results are your insight into how your web services have been performing and getting detailed information on what happened when something goes wrong with your web service.

Assertions

An assertion validates some part of a test's response; you can add multiple assertions to any test. For instance, I would assert that testing assertible.com/signup will return a status code 200.

Environments

An environment contains the required settings for making a request to a specific HTTP endpoint related to a web service. For example, staging.assertible.com could correspond to an environment named staging. This makes it easy to create new tests for known web services.