testing-operations

Automate contract compliance testing and regression test workflows for 3Lens.

Updated Jul 29, 2025

Search Tags:#vitest #testing #contract-testing #lens #software-testing #trace-analysis #regression-tests

Ready to run

npx skills add https://github.com/adriandarian/3Lens --skill testing-operations

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: testing-operations
Source: https://github.com/adriandarian/3Lens/tree/main/.cursor/skills/testing-operations
Command: npx skills add https://github.com/adriandarian/3Lens --skill testing-operations

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Testing operations cover writing contract compliance tests, regression tests, and validating test coverage for 3Lens.

Core Features & Use Cases

Contract Compliance Tests: Tests that validate contract invariants for lens entities.
Regression Tests: Tests that detect regressions by replaying traces and comparing results.
Snapshot Tests: Tests that ensure stable graph and metric outputs.
Live/Offline Parity: Tests that verify results in live mode and offline traces.
Test Patterns: Fidelity checks, attribution checks, and coverage validations.

Quick Start

Run the contract testing workflow to validate invariants and generate regression tests from traces.

Frequently Asked Questions about testing-operations

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate regression tests from trace data?▼

Regression tests are generated by replaying traces and comparing results to detect regressions. This workflow automates the replay process to validate test coverage and ensure stable outputs across the testing ecosystem.

What is contract compliance testing for software systems?▼

Contract compliance testing validates contract invariants for entities within a system. It ensures that specific conditions and rules hold true, verifying that components interact correctly according to defined expectations.

How do I validate live and offline parity in test environments?▼

Live and offline parity validation verifies that results in live mode match offline traces. This ensures consistent behavior and reliable test coverage across different execution environments.

Does this testing workflow support fidelity and attribution checks?▼

Yes, the workflow supports fidelity checks, attribution checks, and coverage validations as core test patterns. These mechanisms validate trace accuracy and ensure proper result sourcing.

Why do my snapshot tests fail when graph outputs change?▼

Snapshot tests fail when graph and metric outputs deviate from established baselines. These tests ensure stable outputs by detecting unexpected structural or numerical changes during regression validation.