CRIS: Accelerating Smarter Releases Through Comprehensive Release Intelligence.
CRIS is an accelerator built by Techment that intelligently selects and executes only the tests impacted by recent code changes by leveraging coverage data, instead of running the entire test suite. This streamlines validation cycles, shortens release timelines, and optimizes QA effort, while maintaining high confidence in build stability and overall product quality.
- Runs only the tests your change touches
- Always re-runs previously failed tests
- Plugs into your existing CI/CD pipeline
- Unified release dashboard for every run
Why Do Teams Slow Down at Release Time?
Full regression runs, long validation cycles, and fragmented reporting turn every release into a bottleneck.
Full Test Suite Runs on Every Commit
Teams run thousands of tests for minor code changes, wasting compute time and slowing CI pipelines.
Long Validation Cycles Delay Releases
Hours long test runs create release bottlenecks, delaying time to market and QA throughput.
No Visibility Into Test Change Relationships
Teams lack insight into which tests are truly impacted by a given code change, leading to over testing.
Failed Tests Are Easily Missed
Previously failed tests can go undetected across releases when file based selection logic is used naively.
Fragmented Release Reporting
QA teams have no unified dashboard to track what changed, what was tested, and what passed or failed per release.
High QA Effort for Each Release
Manual effort to triage results and map test outcomes to specific releases is error prone and time consuming.
Coverage Driven Test Selection, Every Time, Automatically
CRIS uses code coverage data to understand exactly which tests are touched by each change, then executes only those tests, every time, automatically.
Impact Based Test Selection
Leverages coverage data to identify which tests are affected by each file or code change. Not guesswork.
Smart Re-Run Logic
Always re-runs previously failed tests, even when their related source files remain untouched.
Full Suite for Critical Changes
Automatically triggers complete test suite execution when tracked critical files are modified.
Release Dashboard
A unified view of all releases with impacted files, selected tests, and execution outcomes per release.
CI/CD Integration
Plugs directly into Azure DevOps, GitHub Actions, CircleCI, and other popular providers.
Modular & Extensible
Supports Playwright today, with Cypress, Selenium, JUnit, and pytest on the roadmap.
From Commit to Release Report, Automatically
CRIS integrates seamlessly into your existing pipeline. No changes to how developers write code.
Feature Release to Staging
The Development team deploys a release to the staging environment for QA validation.
Pipeline Triggers & App Instruments
A subscribed Azure pipeline builds and deploys the instrumented application to collect code coverage data.
CRIS Analyses Impact
The Test Impact Analyzer determines which test cases are affected based on changed files and coverage mapping.
Impacted Tests Execute
Only the selected tests run inside a Container App Job. Logs capture real time results and outcomes.
Release Report Generated
The CRIS-TIA dashboard shows total, passed, failed, and skipped tests with pass rates for data driven decisions.
Measurable Impact on Every Release
CRIS reduces waste, increases confidence, and gives QA teams the visibility they need to release with certainty.
Works With the Tools You Already Use
CRIS FAQs
What is CRIS?
How does CRIS know which tests to run?
Can CRIS miss previously failed tests?
What happens when critical files change?
Which CI/CD tools does CRIS integrate with?
Which test frameworks does CRIS support?
Stop Running Thousands of Tests for a Ten Line Change
Book a personalised demo and see CRIS select, execute, and report on only the tests that matter.
Request a Demo