Skip to content

docs: refresh test-slice mentions to match 4-slice CI reality#111

Merged
emeraldleaf merged 1 commit into
mainfrom
docs/refresh-test-slice-mentions
Jun 4, 2026
Merged

docs: refresh test-slice mentions to match 4-slice CI reality#111
emeraldleaf merged 1 commit into
mainfrom
docs/refresh-test-slice-mentions

Conversation

@emeraldleaf
Copy link
Copy Markdown
Owner

@emeraldleaf emeraldleaf commented Jun 4, 2026

Summary

After #109 wired Payment + Shipping integration tests into CI, two doc sites still claimed only Catalog + Order slices existed. Surfaced by a doc-drift sweep after the /check-rules audit.

Changes

  • README.md:19 — List all four slices with their containers (Catalog: Postgres+Redis, Order: SQL Server+stubbed Wolverine, Payment: SQL Server, Shipping: Postgres). Rephrase "134 unit + integration slices" as "100+ unit + integration tests" so the precise number stops drifting every PR.
  • docs/architecture.md:546 — Update the slice list to all four; clarify the remaining gap is wire-level cross-service coverage specifically (single-service slices are no longer the gap).

What this is NOT

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Documentation
    • Updated test coverage documentation to reflect current test volume and integration testing strategy.
    • Clarified cross-service integration testing approach, including breakdown of database-touching services and CI execution strategy.

After #109 wired Payment + Shipping integration tests into CI, two doc
sites still claimed only the Catalog + Order slices existed:

- README.md "Verification at every layer" listed only Catalog (Postgres +
  Redis) and Order (SQL Server + stubbed Wolverine). The "134 unit +
  integration slices" count had also drifted to 142.
- docs/architecture.md "Gaps & Future Work" said "CatalogService and
  OrderService single-service slices exist" and framed the cross-service
  gap as the only remaining work.

Surfaced by a doc-drift sweep after the /check-rules audit.

Changes:
- README: list all four slices with their containers; rephrase the test
  count as "100+ unit + integration tests" instead of a precise number
  that drifts every PR.
- architecture.md: update the slice list to all four; clarify that the
  remaining gap is wire-level cross-service coverage specifically.

No rule changes; pure documentation refresh.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@emeraldleaf emeraldleaf merged commit 76f7133 into main Jun 4, 2026
@emeraldleaf emeraldleaf deleted the docs/refresh-test-slice-mentions branch June 4, 2026 03:19
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Jun 4, 2026

Review Change Stack

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: c8523d8c-7d07-4ff3-93bf-3c37856c68fc

📥 Commits

Reviewing files that changed from the base of the PR and between b67ad63 and adc6851.

📒 Files selected for processing (2)
  • README.md
  • docs/architecture.md

Walkthrough

This PR updates documentation to reflect the current test infrastructure. README.md clarifies the Testcontainers integration-test volume and enumerates the four service slices (Catalog, Order, Payment, Shipping) with their respective database and transport configurations. docs/architecture.md expands the cross-service integration test coverage description from two services to four DB-touching services, while identifying the remaining gap as an end-to-end event-flow test over Azure Service Bus.

Changes

Test Coverage Documentation

Layer / File(s) Summary
Test coverage documentation updates
README.md, docs/architecture.md
README verification bullet updated to reflect test count and enumerate Testcontainers slices for Catalog (Postgres + Redis), Order (SQL Server + stubbed Wolverine), Payment (SQL Server), and Shipping (Postgres) with separate CI steps. Architecture documentation updated to describe cross-service integration test coverage across four services and clarify the remaining end-to-end event-flow test gap over Azure Service Bus emulator.

🎯 1 (Trivial) | ⏱️ ~2 minutes

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/refresh-test-slice-mentions

Comment @coderabbitai help to get the list of available commands and usage tips.

@codecov
Copy link
Copy Markdown

codecov Bot commented Jun 4, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant