What is Digy360?

Digy360 serves as a Pluggable Continuous Test Orchestration Pipeline, empowering organizations to execute automated tests with every code change in a continuous manner.

Automated tests are triggered based on the provided requirement ID during code commits. Digy360 utilizes this ID to selectively retrieve necessary BDD steps from Test Management platforms. It then executes corresponding glue code using Digy360-supported Automation Frameworks on compatible Test Execution platforms. Automation results are updated both in Test Management systems and DigyDashboard.

This ensures continuous, controlled, and observable test automation at any given time. Digy360 seamlessly connects various components, fostering true continuity in the Continuous Testing Pipeline:

• Project Management tools
• Test Case Management tools
• Source Code Repository (code)
• Source Code Repository (automation)
• Test Automation Frameworks
• Universal Reporting Dashboard
• AI-based Alerting

These connections are established in a tool, framework, solution, platform, and vendor-agnostic manner, preventing Digy360 from being tied to specific components. Operating on an integration model rather than a migration model, Digy360 allows adoption without the need for migration.

What it is not?

Digy360 differs from traditional DevOps CI/CD platforms; it specifically focuses on being a pluggable Continuous Test Orchestration Pipeline dedicated to running tests continuously within any conventional CICD platform.

Why Digy360?

In the realm of Continuous Integration/Continuous Deployment (CICD) pipelines, the goal is to achieve a truly “continuous” integration and delivery process for every code change. However, this typically involves:

• Building the code/ Unit Testing
• Deploying the code to Test Environment
• Deploying the code to Prod Environment

Notably, the testing component is often overlooked for various reasons:

What is Integration Hub?

The Integration Hub, an integral component of DigyCloud, enables organizations to seamlessly integrate all supported elements of CI/CD with Digy360. This facilitates communication between Digy360 and the integrated components, thereby creating a cohesive Testing Pipeline. This orchestration ensures a continuous and streamlined Testing Pipeline.

• Tests are frequently unreliable, making them unsuitable as gatekeepers for deployment status.
• The feedback cycle is excessively long, with test execution times ranging from a few hours to an impractical number of hours.
• There is no mechanism to selectively run tests associated with a specific code change.in a Test Management agnostic way.
• There is a lack of a comprehensive solution that can seamlessly connect a code commit to a requirement, link those requirements to a set of test cases, map those test cases to automation code, provide reporting, and integrate back into the test case management system in a tool-agnostic, framework-agnostic, solution-agnostic, platform-agnostic, and vendor-agnostic manner.

Digy360 addresses these challenges by making automation execution a genuinely continuous process within any traditional pipeline, all without requiring the migration of existing infrastructure.