You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Automatics Repositories

Repository NameRepository PathBranchDescription
Automatics Orchestrationrdk/tools/automaticsrdk-nextStandalone UI based tool which helps user to trigger executions and view results 
Automatics Corerdk/tools/automatics/automatics-corerdk-next

Main component of Automatics system that manages test execution.

This project is executed in jenkins.

Automatics Propertiesrdk/tools/automatics/automatics-propsrdk-next

Standalone UI based tool where user can configure urls and other data required for test execution

For eg: Base url for REST implementation by partner will be configured in this tool which is used by Automatics orchestration and Automatics core.

Automatics Generic Testsrdk/tools/automatics/generic-automation-testsrdk-next

Holds generic tests for execution. This is the project checkout by jenkins and executes tests in them. This test project is maven dependent on Automatics Core project via transitive dependency with Partner Java API implementation.

Partner Repositories

To use Automatics system, partner has to provide implementation for Providers based API specification at .

There are two types of implementations required from partner.

Project
Description

Partner Java API

implementation


Maven based project implemented based on specification.

This project adds Automatics Core as maven dependency and implements all Java based providers.

Partner implementation project is added as maven dependency in Automatics Generic Tests. Any direct dependencies to Automatics Core in Generic Tests project are

removed and Partner implementation is added as dependency during development and test execution.

Only generic tests, use this project as maven dependency.

Partner REST API 

implementation


REST api implementation based on specification. REST APIs are used by both Automatics orchestration and Automatics Core.
  • No labels