docs(dev): document TDD expected-fail integration test implementation #4338

Open
opened 2026-04-07 19:52:49 +00:00 by freemo · 0 comments
Owner

Documentation Update Issue

Priority: High - Critical for development workflow understanding

Document the implementation of TDD expected-fail tags for integration tests, including the workflow for fixing the 8 tagged failing tests and the coverage threshold restoration process.

Acceptance Criteria

  • Update CONTRIBUTING.md with integration test TDD workflow
  • Document the 8 specific failing tests and their issue numbers (#4329-#4336)
  • Explain the three-tag TDD system for Robot Framework tests
  • Document coverage threshold restoration procedure
  • Add examples of proper TDD tag usage in Robot Framework

Metadata

  • Commit Message: docs(dev): document TDD integration test implementation
  • Branch: docs/tdd-integration-test-workflow

Key Content to Document

TDD Integration Test Workflow

  1. Identified 8 failing integration tests:

    • A2A Version Negotiation (issue #4329)
    • Actor Add Rich Output Contains Type Field (issue #4330)
    • Actor Add Rich Output Contains Config Panel (issue #4331)
    • Actor Add Rich Output Contains Capabilities Panel (issue #4332)
    • Actor Add Rich Output Contains Tools Panel (issue #4333)
    • Actor Add Rich Output Contains Success Line (issue #4334)
    • Actor Show JSON Contains Required Fields (issue #4335)
    • Actor List JSON Returns Array (issue #4336)
  2. TDD Three-tag system for Robot Framework:

    • tdd_issue - Generic filter tag
    • tdd_issue_<N> - Issue reference tag
    • tdd_expected_fail - Behavioral switch for result inversion
  3. Coverage restoration: Temporary 50% → 97% threshold restoration

  • /robot/tdd_expected_fail_listener.py - TDD listener implementation
  • /noxfile.py - Coverage threshold configuration
  • Robot test files with TDD tags

Definition of Done

This issue is complete when:

  • CONTRIBUTING.md updated with comprehensive TDD integration workflow
  • Examples of proper Robot Framework TDD tag usage provided
  • Coverage threshold restoration procedure documented
  • Development team can follow documented workflow
  • PR submitted, reviewed, and merged
## Documentation Update Issue **Priority:** High - Critical for development workflow understanding Document the implementation of TDD expected-fail tags for integration tests, including the workflow for fixing the 8 tagged failing tests and the coverage threshold restoration process. ## Acceptance Criteria - [ ] Update CONTRIBUTING.md with integration test TDD workflow - [ ] Document the 8 specific failing tests and their issue numbers (#4329-#4336) - [ ] Explain the three-tag TDD system for Robot Framework tests - [ ] Document coverage threshold restoration procedure - [ ] Add examples of proper TDD tag usage in Robot Framework ## Metadata - **Commit Message:** `docs(dev): document TDD integration test implementation` - **Branch:** `docs/tdd-integration-test-workflow` ## Key Content to Document ### TDD Integration Test Workflow 1. **Identified 8 failing integration tests:** - A2A Version Negotiation (issue #4329) - Actor Add Rich Output Contains Type Field (issue #4330) - Actor Add Rich Output Contains Config Panel (issue #4331) - Actor Add Rich Output Contains Capabilities Panel (issue #4332) - Actor Add Rich Output Contains Tools Panel (issue #4333) - Actor Add Rich Output Contains Success Line (issue #4334) - Actor Show JSON Contains Required Fields (issue #4335) - Actor List JSON Returns Array (issue #4336) 2. **TDD Three-tag system for Robot Framework:** - `tdd_issue` - Generic filter tag - `tdd_issue_<N>` - Issue reference tag - `tdd_expected_fail` - Behavioral switch for result inversion 3. **Coverage restoration:** Temporary 50% → 97% threshold restoration ## Related Files - `/robot/tdd_expected_fail_listener.py` - TDD listener implementation - `/noxfile.py` - Coverage threshold configuration - Robot test files with TDD tags ## Definition of Done This issue is complete when: - CONTRIBUTING.md updated with comprehensive TDD integration workflow - Examples of proper Robot Framework TDD tag usage provided - Coverage threshold restoration procedure documented - Development team can follow documented workflow - PR submitted, reviewed, and merged
HAL9000 added this to the v3.5.0 milestone 2026-04-08 17:43:07 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
cleveragents/cleveragents-core#4338
No description provided.