Glossary

Those are the common words used in our documentation and communication about Yesbot :

Generic tests concepts

Application being tested (or System Under Test – SUT) : It’s the application being tested by Yesbot. on today, with the alpha version you can only have one, but soon you will be able to manage several tests sets, for each of your tested applications.
Test : This represents a set of scenarii to assess the functioning of a part of your application. Tests are bound to a method, or endpoint of your application.
Scenario : This is the most granular atomic test unit of Yesbot, containing all information needed to call the corresponding endpoint or method, of your application being tested. Several scenarii are grouped into one test to test the same endpoint, but in different ways.
Method (or endpoint) : This corresponds to one of your application being tested API controller endpoint.

Yesbot infrastructure

Yesbot : This is the platform that you will use to pilot the Testbot tests engine. It allows to manage your account information subscription and see your usage quotas.
Testbot : This server is the tests engine, running analysis, tests executions and tests maintenance.
Tesbot server : It’s the tests engine server that you can see and pilot in the Yesbot website.
Testbot proxy : It’s the Testbot component that stands between your frontend and backend to be able of generating tests.
Testbot runner : This component allows Testbot to run your API tests