Jagger
 All Classes Namespaces Files Functions Variables Groups Pages
Providers main page
General info
Provides are providing list of endpoints and queries to distributors.
Endpoint - target for the test (address of System Under Test).
Query - request for System Under Test.
Providers are executed single time before start of the tests. Test run sequence you can find here: Test execution sequence
Example of providers setup in XML:
Below is example of XML test-description section
In current example endpoints are hardcoded and list of queries is empty.
In real life it is more complicated. Endpoints and queries are usually provided as CVS files, property files or as some SUT test service
In this case you need to implement custom provider(s). How to do this you can read here: Custom providers
<!-- begin: following section is used for docu generation - simple providers usage -->
<test-description id="td_googlePageTest" parent="td_default">
<scenario xsi:type="scenario-query-pool">
<query-distributor xsi:type="query-distributor-round-robin"/>
<invoker xsi:type="invoker-class" class="${package}.invoker.PageVisitorInvoker"/>
<endpoint-provider xsi:type="endpoint-provider-list">
<endpoint>http://google.com</endpoint>
<endpoint>http://google.ru</endpoint>
</endpoint-provider>
<query-provider xsi:type="query-provider-list">
<query></query>
</query-provider>
</scenario>
</test-description>
<!-- end: following section is used for docu generation - simple providers usage -->
Variants of proviers available in XML:
endpoint-provider - documentation of endpoint provider element in XML schema
query-provider - documentation of query provider element in XML schema
endpointProviderAbstract - types of endpoint providers available in XML schema. See 'Sub Types' section of man page
queryProviderAbstract - types of query providers available in XML schema. See 'Sub Types' section of man page
How providers mentioned above are implemented you can see in section: Implementations of providers