Techment — Site Header
Techment Accelerator

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.

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.

How It Works
Code Changes
Coverage Analysis
Impacted Tests
Selected
CRIS Comprehensive Release Intelligence System
Faster Validation Cycles
TEST RESULT COVERED FILE RE-RUN
FAILED COVERED FILE CHANGED
PASSED COVERED FILE CHANGED
PASSED COVERED FILE UNTOUCHED
PASSED COVERED FILE UNTOUCHED
SKIPPED COVERED FILE UNTOUCHED
SKIPPED COVERED FILE UNTOUCHED
Shorter Release Timelines
High Confidence in Stability
Improved Product Quality
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.

Less Waste Only the tests impacted by each change run, instead of thousands of tests on every commit.
More Confidence Failed tests always re-run and critical file changes trigger the full suite, keeping build stability high.
Full Visibility One dashboard tracks what changed, what was tested, and what passed or failed per release.

Works With the Tools You Already Use

No migration, no rewrites. CRIS plugs into the pipeline, frameworks, and coverage tooling your teams run today.

CI / CD Pipelines Runs as a step in your existing pipeline
Azure DevOps GitHub Actions GitLab CI Jenkins CircleCI
Test Frameworks Selects at the individual test level
Playwright Cypress Selenium JUnit Pytest
Coverage & Runtimes Reads coverage from your existing tooling
.NET / AltCover Java / JaCoCo JS / Istanbul Python / coverage.py and others

CRIS FAQs

What is CRIS?

CRIS (Comprehensive Release Intelligence System, Smart Regression Tool) 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.

How does CRIS know which tests to run?

CRIS uses code coverage data to understand exactly which tests are touched by each file or code change. Its Test Impact Analyzer maps changed files to affected test cases, so selection is based on real coverage relationships, not guesswork.

Can CRIS miss previously failed tests?

No. CRIS includes smart re-run logic that always re-runs previously failed tests, even when their related source files remain untouched, so failures never go undetected across releases.

What happens when critical files change?

CRIS automatically triggers complete test suite execution when tracked critical files are modified, so high risk changes always get full validation coverage.

Which CI/CD tools does CRIS integrate with?

CRIS plugs directly into Azure DevOps, GitHub Actions, CircleCI, GitLab CI, Jenkins, and other popular providers, with no changes to how developers write code.

Which test frameworks does CRIS support?

CRIS supports Playwright today, with Cypress, Selenium, JUnit, and pytest on the roadmap. It also works with .NET / AltCover for coverage instrumentation and is modular and extensible by design.

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.

Hello popup window