Shorter release cycles with workflow automation

image
When testing software, many manual steps must be repeated, such as starting tests when new artifacts are uploaded, generating reports, sending notifications, and obtaining approvals. These steps are time-consuming, slow down development teams, and delay releases.

By intelligently combining Quality Gates and automated workflows (flow.kit), we significantly improve the approval process for software releases.

The strategy: Quality Gates (Q-Gates)

Q-Gates secure major project milestones through staging and simplify process progress monitoring. Staging includes the Q-Gate plan, which outlines a specific approval process and automatically verifies that all criteria have been met.
You define the framework; one:cx manages the process.
  • Release Q-Gates automatically monitor test coverage and results.
  • Approval Gates specifically request human decisions where needed.
  • Join Q-Gates synchronize multiple process strands at important milestones.
  • Workflow Q-Gates automatically trigger the next steps.

Advantage: If the plan stalls, this information is immediately propagated to all subsequent stages. This makes problems visible immediately rather than days later.

The engine: Automation flow.kit

The Automation flow.kit can be used to automate work steps related to test.guide:
  • Create playbooks,
  • Start execution tasks,
  • Send email notifications,
  • Export results to ALM systems (Jira, Polarion, Codebeamer, etc.).



The individual flows respond to events and then execute user-defined actions fully automatically.
  • New software uploaded?
    flow.kit automatically starts test execution with playbooks.
  • Tests completed?
    flow.kit generates PDF reports and distributes them.
  • Errors detected?
    flow.kit automatically triggers a re-evaluation.
  • Release blocked?
    flow.kit updates the Jira ticket and notifies the team.
In this way, the Automation flow.kit accelerates the completion of individual Q-Gate planning stages in a traceable manner.

Technical highlights:

  • Low code: Build a workflow with pre-built blocks (test.guide, Jira, and various ALM systems)
  • Flexibility: Extendability through custom Python implementation
  • Transparency: Detailed flow reports for each execution and role-based permissions
  • Scalability: ResourceAdapter-based execution on any system
  • ALM integration: Seamless connection to Jira, Polarion, Codebeamer, etc. via REST API


Get started now!
The automated approval processes with Q-Gates and flow.kit are part of our one:cx platform and are available immediately. Start with simple workflows, build your own staging processes step by step, and then watch your release processes run themselves.

Interested in a live demo?
Show us your current processes and we will demonstrate how they can run in record time with one:cx.

Request a demo More about one:cx