Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Setup your Automation Project on the same machine as the QMetry Agent.
  2. Directly run your automated project from Automation > Automation Agent > Registered Agents by scheduling your automation.
  3. While scheduling the automation execution you can directly specify your custom commands (like mvn test, mvn install, or any other framework spcific commands) regardless of your automation and build frameworks - with an added ability to set recurrence of test executions.
  4. The result files will get generated as per your automation project.
  5. Results need to pushed by coding using various methodologies like QMetry Result Push API, Jenkins, Maven, other CI/CD tools.
  6. Test Cases, Test Suites and Test Executions are created as per the result file. Existing test suites can be reused using the key.
  7. You can no longer create any automated test suite (manually). Test executions are differentiated as Automated/Manual. Test suites are no more differentiated as automated or manual.

With this upgrade, automation agents are not tightly coupled with any test suite, and are triggered from the Automation > Automation Agent > Registered Agents.
Results can be pushed using various methodologies like QMetry Result Push API, Jenkins Plugin, Maven, other CI/CD tools.

...