Automated Testing with CI/CD Tools Integration and Public API Exposure

[#1]

Introducing automated testing, AgileTest kicks off 2025 with a major update. My name is Peter from the AgileTest team. Today, let's take a closer look at what automation can do. 

---

CI/CD Integration for Automated Testing

Remote Build Triggers with CI/CD Tools

AgileTest now integrates directly with CI/CD tools such as Bitbucket, GitHub, GitLab, and Jenkins, allowing users to trigger remote builds and automatically import test results.

Once test results are imported, they are automatically linked to Jira test cases, ensuring that test statuses are updated automatically. This reduces manual tracking and provides better visibility into test execution and failure analysis.

Framework Integration for Automated Testing

AgileTest now supports direct test result imports from widely used automation frameworks, including JUnit, NUnit, TestNG, xUnit, Cucumber, Behave, and Robot Framework. This allows teams to seamlessly integrate their existing automated tests into AgileTest without additional setup.

For teams using other frameworks, manual test result uploads are also available, ensuring that AgileTest accommodates diverse testing environments.

Manual Test Result Import for Non-CI/CD Users

For teams that do not use CI/CD tools, AgileTest offers a manual test result import option. This enables users to run automated tests separately, generate reports, and manually upload results into AgileTest.

This option is particularly useful for teams managing hybrid workflows, allowing them to keep all test execution data centralized and accessible within AgileTest.

AgileTest CLI: Automate Without API Calls

With this release, AgileTest introduces a powerful Command-Line Interface (CLI) to replace traditional API calls, providing teams with more control and efficiency over their testing processes.

The AgileTest CLI enables scripting, automation, and integration within CI/CD systems, including Jenkins, GitLab CI, GitHub Actions, and Bitbucket Pipelines. It supports YAML-based configurations, local terminal execution, and Docker environments, offering an alternative to API-based automation while streamlining test imports and remote build triggers.

This feature is designed to reduce complexity and improve automation workflows, ensuring that teams can easily integrate AgileTest into their existing pipelines without relying on direct API calls.

Transition to a Paid Model

Alongside the Automated Testing release, AgileTest is now transitioning to a paid application model. This shift reflects the value of its advanced automation capabilities, as well as AgileTest’s commitment to continuous improvements, innovation, and dedicated support for its users.

For pricing details, visit AgileTest Price or check it out on Atlassian Marketplace.

Why These Updates Are Important

Together, these changes reflect AgileTest’s commitment to supporting the needs of testers. By adding robust automation capabilities, redesigning the interface for improved usability, and enhancing performance, AgileTest ensures users can work more efficiently and achieve better results. 

With the transition to a paid model, AgileTest is also ensuring the long-term sustainability and innovation of its platform, providing continued enhancements and dedicated support to its growing user base.

For more details, please refer to the full release notes here: → [Read Full Details].