Menu
Run integration tests for the Loyalty Points Program using the containerized test suite. All tests are defined in specs/testing.md.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Compile dashboard and loyalty projects in dev mode with hot reload. Dashboard uses npm, loyalty uses Maven with Spring Boot DevTools.
Launch a complete production demo by rebuilding all images and starting the full stack. Use when preparing a fresh demonstration.
Run the development infrastructure stack with Docker Compose. Use when starting, stopping, or managing the dev environment.
Code generation guidelines for this project. Use when writing code, functions, or classes. Enforces English naming, concise comments, and project conventions.
Git commit guidelines for this project. Use when creating commits, writing commit messages, or preparing changes for version control. Enforces conventional commit format and English language.
Documentation guidelines for this project. Use when writing or updating markdown documentation, README files, or specifications. Enforces English language, table alignment, and ASCII diagram formatting.
| name | test |
| description | Run integration tests for the Loyalty Points Program using the containerized test suite. All tests are defined in specs/testing.md. |
| metadata | {"author":"Claude Code","version":"1.1"} |
Run integration tests for the Loyalty Points Program using the portable test container.
This skill runs 24 automated tests across 6 test groups. All test definitions and requirements are in @specs/testing.md.
The tests are implemented in a containerized suite (@it/) that validates the Loyalty Service:
# 1. Build container
cd it && docker build -t loyalty-it .
# 2. Clean data and restart services
docker compose restart redis temporal && sleep 30
# 3. Wait for all services to be healthy
sleep 30
# 4. Run all tests
docker run --network loyalty-frontend loyalty-it http://gateway:8080
# Exit code: 0 = pass, 1 = fail
Why restart Redis and Temporal?
| Group | Tests | Description |
|---|---|---|
| health | H0-H5 (5) | Service health checks |
| core | T1.1-T2.6 (6) | Core features (enroll, earn, spend) |
| saga | T3.1-T3.3 (3) | Saga pattern & compensation |
| grace | T4.1-T4.3 (3) | Grace period & rejoin |
| idempotency | T5.1-T5.3 (3) | Idempotency & transaction tracking |
| errors | T6.1-T6.4 (4) | Error handling & edge cases |
| all | 24 total | All tests |
Run a specific group:
# Clean data first
docker compose restart redis temporal && sleep 30
# Run specific test group
docker run --network loyalty-frontend loyalty-it http://gateway:8080 core
If you need to clean data manually without restarting:
# Clear Redis data
docker compose exec redis redis-cli FLUSHALL
# Restart Temporal to clear workflow state
docker compose restart temporal && sleep 20
Detailed information is in the @it/ component:
| File | Content |
|---|---|
@specs/testing.md | All test definitions and requirements |
@it/QUICKSTART.md | Common patterns and usage examples |
@it/README.md | Full technical documentation |
@it/VALIDATION.md | Architecture and verification checklist |
@it/MANIFEST.md | Component completeness verification |
For troubleshooting, see @it/QUICKSTART.md or @it/VALIDATION.md.