skills.rest
CMTA
CMTAOFFICIAL
Explore all skills by this author →
Website𝕏@cmta_chGitHub

testing

Execute Foundry-based RuleEngine tests with RBAC and Ownable variants.

7|7|Updated Sep 28, 2022
Search Tags:#testing#rbac#solidity#foundry#unit-tests#forge#helper-contracts
One-click install
npx skills add https://github.com/CMTA/RuleEngine --skill testing-cmta
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: testing
Source: https://github.com/CMTA/RuleEngine/tree/main/.claude/skills/testing
Command: npx skills add https://github.com/CMTA/RuleEngine --skill testing-cmta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a standardized approach to organizing and executing Foundry-based tests for the RuleEngine project, including RBAC and Ownable variants, helper contracts, and test utilities.

Core Features & Use Cases

  • Test organization: structure-guided placement of tests under test/ and helpers under utils/ to ensure repeatable results.
  • Test conventions: enforces naming, file layout, and verification patterns described in the repository.
  • Use Case: a developer adds a new RuleEngine feature and uses the provided test templates to validate behavior across variants.

Quick Start

Run the Foundry test suite for RuleEngine using forge test and review the HelperContract and test directories for structure.

Frequently Asked Questions about testing

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

FAQPage Schema
How do I organize and run Foundry tests for RuleEngine contracts?▼

Organize Foundry tests for RuleEngine by placing tests under test/ and helpers under utils/, then execute the suite using `forge test` to validate behavior across RBAC and Ownable variants.

What's the best way to structure Foundry test suites for RBAC and Ownable contract variants?▼

Structure Foundry test suites for RBAC and Ownable variants by following the repository's test directory conventions, utilizing HelperContract suites and test utilities to enforce naming and ensure deterministic verification results.

Does this Foundry testing convention support HelperContract suites and test utilities?▼

Yes, the Foundry testing convention supports HelperContract suites and test utilities, enforcing organization rules, precise test naming, and strict error checking to validate RuleEngine features deterministically.

How do I ensure deterministic test results when adding new RuleEngine features in Solidity?▼

Ensure deterministic test results for new RuleEngine features by applying the provided test templates, adhering to enforced file layout and naming conventions, and checking precise errors across RBAC and Ownable variants.

Why do my Foundry unit-tests fail when verifying RuleEngine behavior across different contract variants?▼

Foundry unit-tests may fail if they do not follow the established test conventions for RuleEngine, which require structure-guided placement, specific naming, and precise error checking across RBAC and Ownable variants.

Do I need Forge to execute unit-tests for the RuleEngine project?▼

Yes, you need Forge from the Foundry toolkit to execute the unit-tests for the RuleEngine project, as the test conventions and directory structures are specifically designed for Foundry-based workflows.

Related Skills

Explore More Software Engineering Skills→
darioloetscdarioloetsc

testing

Organizes and executes Foundry-based tests for the RuleEngine project.

Community
Advanced
cyoteecyotee

forge-testing

Automate Solidity contract testing with Foundry's forge test.

Community
Advanced
tenequmtenequm
32

foundry-solidity

Build and test Solidity smart contracts using Foundry tooling.

Community
Advanced
celo-orgcelo-org
8

evm-hardhat

Guide Hardhat project setup, contract testing, deployment, and verification on EVM networks.

Official
Intermediate