Property Based Testing Skill
Skill Verified ActiveProvides guidance for property-based testing across multiple languages and smart contracts. Use when writing tests, reviewing code with serialization/validation/parsing patterns, designing features, or when property-based testing would provide stronger coverage than example-based tests.
To guide developers in leveraging property-based testing for more robust and comprehensive test coverage, especially for complex logic, serialization, and invariants.
Features
- Detects property-based testing opportunities in code patterns.
- Provides guidance on generating property-based tests and input strategies.
- Offers methods for reviewing and improving existing property-based tests.
- Explains Property-Driven Development for feature design.
- Suggests refactoring patterns to enhance testability.
Use Cases
- Writing stronger tests for serialization/deserialization logic.
- Designing new features with executable specifications via properties.
- Reviewing code for areas that would benefit from property-based tests.
- Improving the quality and coverage of existing property-based tests.
Non-Goals
- Automatically generating PBT tests without developer input or review.
- Performing unit or integration testing directly; it provides guidance.
- Replacing example-based testing entirely; it complements it for specific patterns.
- Testing code with untestable side effects without refactoring.
Practices
- Test Design
- Code Quality
- Software Design
Installation
First, add the marketplace
/plugin marketplace add trailofbits/skills/plugin install property-based-testing@trailofbitsQuality Score
VerifiedTrust Signals
Similar Extensions
Migrate Validate
100Validate pending migrations for foreign key consistency, rollback safety, and best practices
Semgrep Rule Creator
100Creates custom Semgrep rules for detecting security vulnerabilities, bug patterns, and code patterns. Use when writing Semgrep rules or building custom static analysis detections.
Moyu (摸鱼)
100과잉 엔지니어링 패턴이 감지되면 자동으로 활성화됩니다: (1) 사용자가 명시적으로 변경을 요청하지 않은 코드나 파일을 수정하는 경우 (2) 요청되지 않은 새로운 추상화 레이어(class, interface, factory, wrapper)를 생성하는 경우 (3) 요청되지 않은 주석, 문서, JSDoc, 타입 어노테이션을 추가하는 경우 (4) 요청되지 않은 새로운 의존성을 도입하는 경우 (5) 최소한의 편집 대신 파일 전체를 다시 작성하는 경우 (6) diff 범위가 사용자의 요청을 명백히 초과하는 경우 (7) 사용자가 "너무 많아", "거기는 건드리지 마", "X만 변경해", "간단하게", "그만" 등의 신호를 보내는 경우 (8) 발생할 수 없는 시나리오에 대한 에러 처리, 유효성 검사, 방어적 코드를 추가하는 경우 (9) 요청되지 않은 테스트, 설정 스캐폴딩, 문서를 생성하는 경우
Definition Of Done
100Mandatory checks to run before completing any task that touches md files or dart code in this repository.
Openclaw Testing
100Choose, run, rerun, or debug OpenClaw tests, CI checks, Docker E2E lanes, release validation, and the cheapest safe verification path.
Wrap Up Ritual
100End-of-session ritual that audits changes, runs quality checks, captures learnings, and produces a session summary. Use when saying "wrap up", "done for the day", "finish coding", or ending a coding session.