ace-test 0.6.1 → 0.7.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 03f1568b0abaf1ec15db4503fb0deb7022d8174dba577270eef50578a79ed750
-  data.tar.gz: dc057abd1b2f18b9109fdeec968cb334a5ece633b18dcaaceedb86a6fe124f78
+  metadata.gz: 0f6c8febd7cff4963e31d233c0c200bc3616698238b5417ba8f4ae506409dba5
+  data.tar.gz: 99ff797e28b835cf3d47ff4e8c4727359c2a02419f14d7100588cc4eb54f996e
 SHA512:
-  metadata.gz: 3e72c6d07bf3b2159cadf2d7f7943af58c0ad6c93948fdb896c2351723d46e8c191c1aab5b16c8d1fe03042a9e4aa279701305c0778a55314bc2f3c7b1c6447a
-  data.tar.gz: da5c418d16c6276c265c1bd59048875b77a9caf2dfca7fd55fd77c331754fc01be165f0dd70b55c48b881691d86c95f23b1983f720805ef18f87370bf6adfa78
+  metadata.gz: 58336d9f304a219d0967bee8a57cbb748908b63a0252bc351ec3e726f4eaabc0026eed1fffdf1b1c6a932f78080bf39909379a04aea222056f80280d1bc21e7b
+  data.tar.gz: e457f888095656701f9c468e25746e40c9dddd3af35b8ca3dfaf57c3cfbaa016854c2e851b77f5f32b202bada727b1a537887fafdfe6a1daed7fbc09fa5bf2e0

data/CHANGELOG.md

@@ -6,6 +6,46 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.7.2] - 2026-04-13
+
+### Changed
+- **ace-test v0.7.2**: Moved package coverage to test/fast and updated the testing contract.
+
+
+## [0.7.1] - 2026-04-11
+
+### Technical
+- Added the missing `0.7.0` changelog release section so package release history aligns with the shipped version line.
+
+## [0.7.0] - 2026-04-11
+
+### Changed
+- Migrated deterministic package coverage to `test/fast/` and refreshed package docs to publish the fast-only testing contract (`ace-test ace-test` / `ace-test ace-test all`) without introducing `test/feat/` or `test/e2e`.
+
+## [0.6.6] - 2026-04-11
+
+### Technical
+- Updated packaged testing agents to use `target` consistently for package-level scopes and refreshed examples around `fast` and `feat`.
+
+## [0.6.5] - 2026-04-11
+
+### Technical
+- Synced the canonical `as-test-verify-suite` skill description with the new assignment verification contract so packaged step metadata matches `ace-test <package> all` plus plain `ace-test-suite`.
+
+## [0.6.4] - 2026-04-11
+
+### Changed
+- Rewrote testing guides and responsibility-map templates to define the public ACE testing taxonomy as `fast`, `feat`, and `e2e`.
+- Added repository-level testing-pattern guidance that explains the new directory layout and command surface.
+
+### Changed
+- Expanded `as-test-verify-suite` canonical skill metadata so public `verify-test-suite` assign-step discovery is skill-owned while keeping step-template rendering in catalog YAML.
+
+## [0.6.2] - 2026-03-29
+
+### Technical
+- Normalized published gem metadata so RubyGems and Ruby Toolbox use current release information instead of the 1980 fallback date.
+
 ## [0.6.1] - 2026-03-29
 
 ### Technical

data/README.md

@@ -36,5 +36,17 @@
 
 **Verify full-suite health** - use `/as-test-verify-suite` to confirm that the complete test suite passes after changes, coordinating with [`ace-test-runner`](../ace-test-runner) for execution.
 
+## Testing Contract
+
+This package is **fast-only** in the ACE testing model.
+
+- Deterministic coverage lives under `test/fast/`.
+- This migration does not introduce `test/feat/` or `test/e2e/` for this package.
+
+Verification commands:
+
+- `ace-test ace-test`
+- `ace-test ace-test all`
+
 ---
 [Getting Started](docs/getting-started.md) | [Usage Guide](docs/usage.md) | [Handbook - Skills, Agents, Templates](docs/handbook.md) | Part of [ACE](https://github.com/cs3b/ace)

data/handbook/agents/profile-tests.ag.md

@@ -5,7 +5,7 @@ expected_params:
   required: []
   optional:
   - count: 'Number of slowest tests to show (default: 10)'
-  - target: 'Test target - file, directory, or group'
+  - target: 'Test target - file, directory, or target'
   - threshold: 'Only show tests exceeding this time (e.g., 100ms)'
 last_modified: '2026-01-22'
 type: agent
@@ -28,7 +28,7 @@ Your primary role is to analyze test performance and suggest optimizations:
 # Profile 10 slowest tests
 ace-test --profile 10
 
-# Profile slowest tests in a specific group
+# Profile slowest tests in a specific target
 ace-test atoms --profile 20
 
 # Profile a specific test file

data/handbook/agents/test.ag.md

@@ -4,7 +4,7 @@ description: Run tests with smart defaults and helpful diagnostics
 expected_params:
   required: []
   optional:
-  - target: 'Test target - file path, directory (atoms, molecules), or group name'
+  - target: 'Test target - file path, directory (atoms, molecules), or target name'
   - profile: 'Profile N slowest tests to identify performance issues'
   - verbose: 'Show detailed test output'
 last_modified: '2026-01-22'
@@ -42,11 +42,11 @@ ace-test-suite
 # Run single test file
 ace-test test/atoms/pattern_analyzer_test.rb
 
-# Run test directory/group
+# Run test directory/target
 ace-test atoms
 ace-test molecules
 ace-test organisms
-ace-test integration
+ace-test feat
 ```
 
 ### Profile Tests
@@ -54,7 +54,7 @@ ace-test integration
 # Profile 10 slowest tests
 ace-test --profile 10
 
-# Profile slowest tests in a group
+# Profile slowest tests in a target
 ace-test atoms --profile 10
 ```
 

data/handbook/guides/test-organization.g.md

@@ -9,36 +9,35 @@ ace-docs:
 
 # Test Organization
 
-## Flat Directory Structure
+## Top-Level Test Structure
 
-All ACE gems use a **flat test directory structure** that mirrors the ATOM architecture:
+All ACE gems should converge on three top-level test directories:
 
 ```
 test/
 ├── test_helper.rb
-├── search_test.rb              # Main module test
-├── atoms/
-│   ├── pattern_analyzer_test.rb
-│   ├── result_parser_test.rb
-│   └── tool_checker_test.rb
-├── molecules/
-│   ├── preset_manager_test.rb
-│   └── git_scope_filter_test.rb
-├── organisms/
-│   ├── unified_searcher_test.rb
-│   └── result_formatter_test.rb
-├── models/
-│   └── search_result_test.rb
-└── integration/
-    └── cli_integration_test.rb
+├── fast/
+│   ├── atoms/
+│   ├── molecules/
+│   ├── organisms/
+│   ├── models/
+│   └── commands/
+├── feat/
+│   └── cli_contract_test.rb
+├── e2e/
+│   └── TS-PACKAGE-001-scenario/
+│       └── scenario.yml
+├── fixtures/
+└── support/
 ```
 
 ## Key Conventions
 
-- **Flat structure**: `test/atoms/`, not `test/ace/search/atoms/`
+- **Top-level categories**: `test/fast/`, `test/feat/`, `test/e2e/`
+- **Fast sublayers mirror ATOM**: atoms, molecules, organisms, models, commands
 - **Suffix naming**: `pattern_analyzer_test.rb`, not `test_pattern_analyzer.rb`
-- **Layer directories match ATOM architecture**: atoms, molecules, organisms
-- **Integration tests in separate `integration/` directory**
+- **Deterministic feature tests live in `test/feat/`**
+- **Scenario workflows live in `test/e2e/TS-*/`**
 
 ## Benefits
 
@@ -47,7 +46,7 @@ test/
 - Consistent across all ACE gems
 - Less nesting = simpler paths
 
-See `ace-taskflow/test/` for reference implementation.
+Use `ace-b36ts/test/` as the reference implementation for the new layout.
 
 ## Naming Conventions
 
@@ -137,4 +136,4 @@ end
 ## Related Guides
 
 - [Testing Philosophy](guide://testing-philosophy) - Why this structure
-- [Mocking Patterns](guide://mocking-patterns) - Test isolation patterns
+- [Mocking Patterns](guide://mocking-patterns) - Test isolation patterns

data/handbook/guides/test-performance.g.md

@@ -242,7 +242,7 @@ end
 | ace-git | `with_mock_repo_load` | Combines 6 stubs for RepoStatusLoader |
 | ace-git | `with_mock_diff_orchestrator` | ConfigLoader + DiffGenerator + DiffFilter |
 | ace-git-secrets | `with_rewrite_test_mocks` | gitleaks + rewriter + working directory |
-| ace-taskflow | `with_real_test_project` | ConfigResolver + project setup |
+| ace-task | `with_real_test_project` | ConfigResolver + project setup |
 | ace-docs | `with_empty_git_diff` | Simple DiffOrchestrator stub |
 | ace-review | `stub_synthesizer_prompt_path` | ace-nav subprocess stub |
 

data/handbook/guides/testable-code-patterns.g.md

@@ -89,7 +89,7 @@ The CLI entry point (exe/ace-*) should handle status codes and exit only at the
 
 ```ruby
 #!/usr/bin/env ruby
-# exe/ace-taskflow
+# exe/ace-task
 
 require_relative "../lib/ace/taskflow"
 

data/handbook/guides/testing-philosophy.g.md

@@ -11,19 +11,17 @@ ace-docs:
 
 ## The Testing Pyramid
 
-ACE follows a strict testing pyramid with clear IO boundaries:
+ACE follows a strict three-level taxonomy with clear IO boundaries:
 
 | Layer | Location | IO Policy | Purpose |
 |-------|----------|-----------|---------|
-| **Unit (atoms)** | `test/atoms/` | **No IO** | Test pure logic in isolation |
-| **Unit (molecules)** | `test/molecules/` | **No IO** | Test component composition |
-| **Unit (organisms)** | `test/organisms/` | **Mocked IO** | Test business logic with stubbed boundaries |
-| **Integration** | `test/integration/` | **Mocked IO** | Test CLI/API surface with stubbed externals |
-| **E2E** | `test/e2e/TS-*/scenario.yml` | **Real IO** | Validate the real system works |
+| **Fast** | `test/fast/` | **No real IO** | Default fast loop for isolated package behavior |
+| **Feat** | `test/feat/` | **Controlled local IO** | Deterministic feature and CLI contract coverage |
+| **E2E** | `test/e2e/TS-*/scenario.yml` | **Real workflow IO** | Validate real user workflows in sandbox |
 
 ## IO Isolation Principle
 
-**Default: No IO in unit tests.** This means:
+**Default: No real IO in fast tests.** This means:
 
 - **No file system**: Use `MockGitRepo` or inline strings, not `File.read`
 - **No network**: Use `WebMock` stubs, not real HTTP calls
@@ -36,9 +34,16 @@ ACE follows a strict testing pyramid with clear IO boundaries:
 - Tests are deterministic (no flaky failures)
 - CI doesn't need special setup
 
-## When Real IO is Allowed
+## When Local IO is Allowed
 
-Real IO belongs in **E2E tests only** (`test/e2e/TS-*/`):
+Controlled local IO belongs in **feat** tests (`test/feat/`):
+
+- local subprocesses
+- tempdirs and filesystem setup
+- config cascade and CLI contract checks
+- deterministic package-level feature validation
+
+Real workflow IO belongs in **E2E** (`test/e2e/TS-*/`):
 
 - Executed by an agent, not the test runner
 - Verify the full system works end-to-end
@@ -59,7 +64,8 @@ Writing tests first drives design and ensures testability. Follow the Red-Green-
 
 ### 2. Isolation
 
-- Unit tests should mock dependencies to test the unit in isolation
+- Fast tests should stub boundaries and stay in-process
+- Feat tests may cross controlled local boundaries, but should not depend on live external services
 - Ensure tests clean up after themselves (reset state, delete created files/records)
 - Tests must be independent and runnable in any order
 
@@ -79,4 +85,4 @@ Writing tests first drives design and ensures testability. Follow the Red-Green-
 
 - [Test Organization](guide://test-organization) - Directory structure and naming
 - [Mocking Patterns](guide://mocking-patterns) - How to isolate tests
-- [Testing TDD Cycle](guide://testing-tdd-cycle) - Implementing the task cycle
+- [Testing TDD Cycle](guide://testing-tdd-cycle) - Implementing the task cycle

data/handbook/guides/testing.g.md

@@ -19,44 +19,32 @@ conventions should be documented in `dev-taskflow/testing-guide.md` (if it exist
 
 ## 1. Testing Strategy
 
-1. **Test Types:** Employ a mix of test types appropriate for the project:
-    * **Unit Tests:** Test individual classes or methods in isolation. Mock dependencies. Focus on logic
-      correctness.
-    * **Integration Tests:** Test the interaction between two or more components (e.g., class and its
-      dependency, module interactions, API client and service). May involve partial mocking or real
-      dependencies in controlled environments.
-    * **End-to-End (E2E) / System Tests:** Test complete user flows or system functionalities, often
-      interacting with real external dependencies or a fully deployed environment. These are typically
-      slower and less frequent.
-    * **Performance Tests:** Measure response time, throughput, resource usage under specific conditions
-      or load.
-    * **Security Tests:** Identify vulnerabilities (e.g., penetration testing, dependency scanning).
-
-2. **Directory Structure:** Organize tests logically, typically mirroring the source code structure.
-    *(Example structure - adjust based on project)*
+1. **Public test categories:** ACE standardizes on three public categories:
+    * **Fast:** isolated package tests under `test/fast/`; no real subprocess, network, or session IO.
+    * **Feat:** deterministic feature tests under `test/feat/`; controlled local IO is allowed.
+    * **E2E:** agent-driven workflows under `test/e2e/`; real sandboxed workflow validation.
+
+2. **Directory Structure:** Organize tests around those three top-level folders.
 
     ```text
     project-root/
-    └── tests/  # Or 'spec/'
-        ├── unit/
-        │   └── my_module/
-        │       └── my_class_tests.ext # Use appropriate extension
-        ├── integration/
-        │   └── service_integration_tests.ext
+    └── test/
+        ├── fast/
+        │   ├── atoms/
+        │   ├── molecules/
+        │   ├── organisms/
+        │   └── models/
+        ├── feat/
+        │   └── cli_contract_test.rb
         ├── e2e/
-        │   └── user_workflow_tests.ext
-        ├── performance/
-        │   └── load_test.ext
-        ├── fixtures/ # Test data files (e.g., YAML, JSON)
-        ├── support/  # Test helpers, shared contexts, custom matchers
-        │   └── helpers.ext
-        └── test_helper.ext # Or 'spec_helper.ext' - Test configuration
+        │   └── TS-PACKAGE-001-scenario/
+        │       └── scenario.yml
+        ├── fixtures/
+        ├── support/
+        └── test_helper.rb
     ```
 
-    *(Refer to `docs/blueprint.md` for the project's actual structure)*
-
-3. **Test Pyramid:** Aim for a healthy test pyramid: many fast unit tests at the base, fewer integration
-   tests, and even fewer slow E2E tests at the top.
+3. **Test Pyramid:** Aim for many `fast` tests, fewer `feat` tests, and the smallest number of `e2e` scenarios.
 
 ## 2. Writing Good Tests
 
@@ -76,7 +64,7 @@ easier to guide the AI effectively.
 * **Stateless Components:** Where possible, favor stateless components or functions, as state
   management adds complexity to testing.
 
-Following these principles makes it easier to write focused unit tests and provide clearer instructions
+Following these principles makes it easier to write focused fast tests and provide clearer instructions
 to an AI agent when generating or modifying code.
 
 1. **Clarity:**
@@ -85,7 +73,8 @@ to an AI agent when generating or modifying code.
     * Keep tests focused on a single behavior or requirement.
 
 2. **Isolation:**
-    * Unit tests should mock dependencies to test the unit in isolation.
+    * Fast tests should mock or fake dependencies and stay in-process.
+    * Feat tests may use controlled local IO when that is the behavior under test.
     * Ensure tests clean up after themselves (reset state, delete created files/records) to avoid
       interference. Use `before`/`after` hooks carefully.
 
@@ -145,9 +134,9 @@ to an AI agent when generating or modifying code.
 ## 8. Test Performance Optimization
 
 For detailed patterns on test performance optimization including:
-- Performance targets by test layer (Unit <10ms, Integration <500ms, E2E <2s)
+- Performance targets by test layer (Fast <10ms for atoms, Feat <500ms when practical, E2E slower by design)
 - Composite test helpers (reduce deep nesting)
-- E2E to integration migration ("ONE E2E per file" rule)
+- E2E to feat migration when deterministic coverage is possible
 - Subprocess stubbing patterns (Open3, DiffOrchestrator)
 - Sleep stubbing for retry tests
 - Zombie mocks detection and prevention
@@ -167,4 +156,4 @@ See: [Test Performance Guide](guide://test-performance)
 
 * [Troubleshooting Workflow](guide://debug-troubleshooting.g)
 * Relevant Workflow Instructions: [`work-on-task.wf.md`](wfi://task/work) (includes testing
-  guidance), [`analyze-failures.wf.md`](wfi://test/analyze-failures) (for classifying failing tests before changes), [`fix-tests.wf.md`](wfi://test/fix) (for applying fixes using analysis output)
+  guidance), [`analyze-failures.wf.md`](wfi://test/analyze-failures) (for classifying failing tests before changes), [`fix-tests.wf.md`](wfi://test/fix) (for applying fixes using analysis output)

data/handbook/skills/as-test-verify-suite/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: as-test-verify-suite
-description: Verify test suite health and enforce performance budgets
+description: Run modified-package deterministic verification plus the default fast monorepo suite
 # bundle: wfi://test/verify-suite
 # agent: general-purpose
 user-invocable: true
@@ -24,10 +24,9 @@ integration:
     - opencode
     - pi
 assign:
-  source: wfi://test/verify-suite
   steps:
     - name: verify-test-suite
-      description: Run package test suites with profiling to verify correctness and performance
+      description: Run modified-package deterministic verification plus the default fast monorepo suite
       intent:
         phrases:
           - "run tests"
@@ -35,6 +34,19 @@ assign:
           - "verify tests"
           - "test changes"
           - "check tests"
+      prerequisites:
+        - name: work-on-task
+          strength: recommended
+          reason: "Should have code changes to verify"
+      produces: [test-results]
+      consumes: [code-changes]
+      context:
+        default: null
+        reason: "Test execution needs access to project environment"
+      when_to_skip:
+        - "No code changes that could affect tests (documentation-only)"
+        - "Tests were already run and profiled in a previous step"
+      effort: light
       tags: [testing, verification, performance]
 skill:
   kind: workflow

data/handbook/templates/test-responsibility-map.template.md

@@ -18,21 +18,20 @@ ace-docs:
 
 - Total behaviors: {{count}}
 - High risk: {{high_risk_count}}
-- Unit tests planned: {{unit_count}}
-- Integration tests planned: {{integration_count}}
+- Fast tests planned: {{fast_count}}
+- Feat tests planned: {{feat_count}}
 - E2E tests planned: {{e2e_count}}
 
 ## Behaviors and Coverage
 
 | Behavior | Risk | Layer | Test File / ID | Source of Truth | Notes |
 |----------|------|-------|----------------|-----------------|-------|
-| {{behavior}} | High/Med/Low | Unit/Integration/E2E | {{test_file}} | {{source}} | {{notes}} |
+| {{behavior}} | High/Med/Low | Fast/Feat/E2E | {{test_file}} | {{source}} | {{notes}} |
 
 ### Layer Legend
 
-- **Unit (atoms)**: Pure logic, no I/O, <10ms
-- **Unit (molecules)**: Composed logic, stubbed I/O, <50ms
-- **Integration (organisms)**: Component wiring, stubbed external, <500ms
+- **Fast**: Isolated package tests in `test/fast`, no real external IO
+- **Feat**: Deterministic feature tests in `test/feat`, controlled local IO
 - **E2E**: Real I/O, sandboxed, seconds
 
 ### Risk Legend
@@ -72,8 +71,8 @@ Critical workflows requiring E2E validation:
 
 ## Action Items
 
-- [ ] Create unit tests for: {{list}}
-- [ ] Create integration tests for: {{list}}
+- [ ] Create fast tests for: {{list}}
+- [ ] Create feat tests for: {{list}}
 - [ ] Create E2E test: TS-{{AREA}}-{{NNN}}
 - [ ] Remove redundant tests: {{list}}
 - [ ] Update fixtures: {{list}}
@@ -89,4 +88,4 @@ Critical workflows requiring E2E validation:
 
 ## Notes
 
-{{additional_notes}}
+{{additional_notes}}

data/handbook/workflow-instructions/test/analyze-failures.wf.md

@@ -90,7 +90,7 @@ Produce this section before exiting:
 
 | Failure | Category | Evidence | Fix Target | Fix Target Layer | Primary Candidate Files | Fallback Candidate Files | Do-Not-Touch Boundaries | Confidence | Disconfirming Check |
 |---|---|---|---|---|---|---|---|---|---|
-| path/to/test_file.rb:TestName | implementation-bug | stacktrace + behavior mismatch summary | implementation code | implementation | app/service.rb, app/model.rb | test/integration/foo_test.rb | test/e2e/** | high | run related tests after patch |
+| path/to/test_file.rb:TestName | implementation-bug | stacktrace + behavior mismatch summary | implementation code | implementation | app/service.rb, app/model.rb | test/feat/foo_test.rb | test/e2e/** | high | run related tests after patch |
 ```
 
 Then include:
@@ -117,4 +117,4 @@ Then include:
 - No-touch boundaries are explicit per failure
 - A single autonomous chosen fix decision is present per failure
 - A prioritized first failure is selected
-- No code/test edits were made in this workflow
+- No code/test edits were made in this workflow

data/handbook/workflow-instructions/test/create-cases.wf.md

@@ -372,7 +372,7 @@ end
    ```
 
    ```
-   .ace-taskflow/v.X.Y.Z/test-cases/
+   .ace-task/v.X.Y.Z/test-cases/
    ├── feature-authentication-tests.md
    ├── api-endpoint-tests.md
    └── performance-benchmarks.md

data/handbook/workflow-instructions/test/optimize.wf.md

@@ -279,7 +279,7 @@ Create retro or update test helper comments:
 # - with_mock_lint_context helper stubs all validators
 # - Real CLI tests moved to test/e2e/
 #
-# See: .ace-taskflow/.../retros/<timestamp>-<package>-test-optimization.md
+# See: .ace-task/.../retros/<timestamp>-<package>-test-optimization.md
 ```
 
 ## Common Optimization Patterns

data/handbook/workflow-instructions/test/plan.wf.md

@@ -287,7 +287,7 @@ Output the Test Responsibility Map document:
 ## Output
 
 The test plan should be saved to:
-- Task folder: `.ace-taskflow/.../task-XXX/test-plan.md`
+- Task folder: `.ace-task/.../task-XXX/test-plan.md`
 - Or reviewed in conversation before implementation
 
 ## Checklist Before Implementation

data/lib/ace/test/version.rb

@@ -2,6 +2,6 @@
 
 module Ace
   module Test
-    VERSION = "0.6.1"
+    VERSION = "0.7.2"
   end
 end

metadata

@@ -1,13 +1,13 @@
 --- !ruby/object:Gem::Specification
 name: ace-test
 version: !ruby/object:Gem::Version
-  version: 0.6.1
+  version: 0.7.2
 platform: ruby
 authors:
 - Michal Czyz
 bindir: exe
 cert_chain: []
-date: 1980-01-02 00:00:00.000000000 Z
+date: 2026-04-20 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler