Open Source Tests (Unit, Integration, System) or Provide Directory for Community Tests
- Dominant language
- TypeScript
- Stars
- 979
- Forks
- 132
- Avg merge
- 9h 23m
- Merged PRs (30d)
- 8
Description
**Description:**
Thank you for open-sourcing AI Playground! While working on creating some initial tests, I noticed that the `service/test/` directory is currently ignored by the `.gitignore` configuration. To avoid conflicts, I’ve placed my tests in a `tests` directory at the project root.
---
**Proposal:**
1. **Open Source Existing Tests:** Include existing unit, integration, and system tests from `service/test/` to ensure all contributions are validated against a consistent set of tests.
2. **Designate a Directory for Community Tests:** If including existing tests isn’t feasible, establish a designated directory for community-contributed tests. I’m currently using `tests` at the project root but am open to other structures.
---
**Benefits:**
- **Improved Code Quality:** A consistent test suite across all levels (unit, integration, system) helps maintain high code quality and prevent regressions.
- **Enhanced Community Engagement:** A clear structure for tests encourages contributions and ensures smooth integration of new features.
---
**Conclusion:**
A clear approach to testing will greatly benefit AI Playground. I’m happy to assist with integrating tests or [share examples](https://github.com/zimm0140/AI-Playground/tree/main/tests/unit/service). I appreciate your feedback and look forward to collaborating on the best solution.
Contributor guide
Assessment
This issue has not been assessed yet.