Tested

API_TEST_EXECUTION_SUMMARY.md

@@ -0,0 +1,38 @@
+# CryptoFlash API Test Execution Summary
+
+## Overview
+This file captures the execution of the API test plan for the CryptoFlash project.
+
+## Changes made
+- Added controller tests for API endpoints:
+  - `src/test/java/jar/controller/MarketControllerTest.java`
+  - `src/test/java/jar/controller/UserControllerTest.java`
+  - `src/test/java/jar/controller/OrderControllerTest.java`
+  - `src/test/java/jar/controller/AdminControllerTest.java`
+- Updated `pom.xml` to include:
+  - `spring-boot-starter-test`
+  - `spring-boot-starter-validation`
+- Added request validation for `OrderController.OrderRequest` in `src/main/java/jar/controller/OrderController.java`.
+- Documented execution summary in `API_TEST_GUIDE.md`.
+
+## Commands executed
+```bash
+./mvnw test -q
+./mvnw -Djava.version=21 test -q
+./mvnw -Djava.version=21 -Dtest=MarketControllerTest test -q
+./mvnw -Djava.version=21 -Dtest=MarketControllerTest,UserControllerTest,OrderControllerTest,AdminControllerTest test -q
+```
+
+## Environment notes
+- Local environment uses Java 21.
+- The project `pom.xml` originally specified Java 25, so tests were executed with `-Djava.version=21`.
+- Full application test execution still requires a running MongoDB and Redis instance.
+
+## Result
+- The new controller tests passed successfully when run together:
+  - `./mvnw -Djava.version=21 -Dtest=MarketControllerTest,UserControllerTest,OrderControllerTest,AdminControllerTest test -q`
+- Exit status: `0`
+
+## Notes
+- Existing `CryptoflashApplicationTests` may fail in the current environment when MongoDB or Redis are not available.
+- The execution summary has been added to `API_TEST_GUIDE.md` and also saved in this standalone file.

API_TEST_EXECUTION_SUMMARY_RUN2.md

@@ -0,0 +1,47 @@
+# CryptoFlash API Test Execution Summary (Run 2)
+
+## Overview
+
+This document captures a second execution of the API test plan for CryptoFlash.
+It preserves the existing summary file by writing a new record under `API_TEST_EXECUTION_SUMMARY_RUN2.md`.
+
+## Execution Date
+
+- June 1, 2026
+
+## Scope
+
+- Verified the focused controller test suite for Market, User, Order, and Admin APIs.
+- Used the same targeted Maven command as the prior run.
+- Did not start application containers for this execution.
+
+## Commands Used
+
+```bash
+wsl -d Ubuntu -- bash -lc 'cd /home/pedro/projects/lm-aide/CryptoFlash && ./mvnw -Djava.version=21 -Dtest=MarketControllerTest,UserControllerTest,OrderControllerTest,AdminControllerTest test -q; echo EXIT_CODE:$?'
+```
+
+## Execution Result
+
+- Controller tests executed successfully.
+- Maven returned `EXIT_CODE:0`.
+- The run produced Spring MockMvc initialization logs and validation warnings from Mockito, but no test failures.
+
+## Verified Test Coverage
+
+- `MarketControllerTest`
+- `UserControllerTest`
+- `OrderControllerTest`
+- `AdminControllerTest`
+
+## Notes
+
+- This run validates the standalone controller API tests in the current development environment.
+- Full application tests still require MongoDB and Redis to be available for end-to-end or integration scenarios.
+- The actual command output included expected validation handling for invalid order requests and missing headers.
+
+## Next Steps
+
+1. If you want to validate the full app behavior, start the containers from `docker-compose-dev.yml`.
+2. Run the full Maven suite or the integration tests once MongoDB and Redis are available.
+3. Preserve this run record alongside the existing summary for comparison.

API_TEST_EXECUTION_SUMMARY_RUN3.md

@@ -0,0 +1,38 @@
+# CryptoFlash API Test Execution Summary (Run 3 - Integration)
+
+## Overview
+
+This document captures an integration run that starts the full application and verifies basic end-to-end endpoints against running MongoDB and Redis containers.
+
+## Execution Date
+
+- June 1, 2026
+
+## Commands Used
+
+```bash
+wsl -d Ubuntu -- bash -lc 'cd /home/pedro/projects/lm-aide/CryptoFlash && ./mvnw -Djava.version=21 -Dtest=EndToEndTest test -q; echo EXIT_CODE:$?'
+```
+
+## Execution Result
+
+- The application started inside the test (Spring Boot v4.0.2) and connected to the running MongoDB replica set and Redis cluster.
+- `EndToEndTest` executed successfully; Maven returned `EXIT_CODE:0`.
+- Logs indicate successful seeding of users and Redis consumer group initialization.
+
+## Verified Endpoints
+
+- `GET /api/market/symbols` returned a non-empty array.
+- `GET /api/admin/health` returned 200 and a non-empty body.
+
+## Notes
+
+- This run confirms the application can start and reach MongoDB and Redis configured by `docker-compose-dev.yml`.
+- The integration test is minimal by design; expand with additional end-to-end flows if you want broader coverage.
+
+## Next Steps
+
+1. Expand `EndToEndTest` with additional scenarios (order placement, replay trigger, user trades).
+2. Add a CI job to run integration tests against an ephemeral Docker environment.
+3. Save additional run artifacts (logs, jacoco) if needed.
+

API_TEST_EXECUTION_SUMMARY_RUN4.md

@@ -0,0 +1,44 @@
+# CryptoFlash API Test Execution Summary (Run 4 - Expanded Integration)
+
+## Overview
+
+This record captures an expanded integration run that exercises additional end-to-end scenarios:
+- user profile
+- place order
+- order book
+- candles
+- trigger replay
+
+## Execution Date
+
+- June 1, 2026
+
+## Commands Used
+
+```bash
+wsl -d Ubuntu -- bash -lc 'cd /home/pedro/projects/lm-aide/CryptoFlash && ./mvnw -Djava.version=21 -Dtest=EndToEndTest test'
+```
+
+## Execution Result
+
+- Tests executed: 7
+- Failures: 0
+- Errors: 0
+- Build: SUCCESS
+- Observations: Application started, connected to MongoDB and Redis; users already seeded; market replay engine ran but found no candles (expected if collection empty); order placement created a resting order in the buy book.
+
+## Verified Scenarios
+
+- `GET /api/market/symbols` returned a non-empty list.
+- `GET /api/admin/health` returned 200.
+- `GET /api/users/SIM_USER_001` returned seeded user data.
+- `POST /api/orders` placed a valid order with header `X-User-ID` and returned 201.
+- `GET /api/orders/book/BTCUSD` returned an order book structure.
+- `GET /api/market/candles/BTCUSD?limit=5` returned an array (may be empty).
+- `GET /api/admin/trigger-replay` returned a success message.
+
+## Next Steps
+
+- Expand tests to cover negative scenarios (invalid orders, missing headers).
+- Add CI job that spins up ephemeral Docker services and runs `EndToEndTest`.
+- Optionally persist run logs and artifacts to `target/` for traceability.