-
Notifications
You must be signed in to change notification settings - Fork 2
TestingIndex
Maria Martinez edited this page Sep 18, 2026
·
1 revision
Central index for automated testing practices, tools, and execution across the Forest Client project.
We maintain a strict quality threshold of minimum 80% test coverage for all new or modified logic. Automated test suites execute on every pull request via GitHub Actions (.github/workflows/analysis.yml).
| Document | Scope | Tools |
|---|---|---|
| Frontend Testing | Unit and component testing for Vue 3 SFCs, composables, and validators. | Vitest, Vue Test Utils, Happy-DOM |
| Backend Testing | Reactive service unit tests and containerized integration tests. | JUnit 5/6, Mockito, Testcontainers, StepVerifier |
| Cypress BDD Guide | Full end-to-end user journey tests authored in plain English Gherkin specifications. | Cypress, Cucumber, Gherkin BDD |
This wiki serves as the central documentation and knowledge base for the Forests Client Management System, maintained by the British Columbia Ministry of Forests.
Please Note:
- This wiki is a living document maintained by the development team and contributors.
- When making substantial architectural or code changes, remember to update the corresponding wiki documentation.
- Always verify critical environment configurations against team vaults and OpenShift secret managers.
Have questions, found a documentation discrepancy, or need clarification?
- Questions or Bug Reports: Open an issue in the GitHub repository
- Pull Requests: Submit code or doc improvements via Pull Requests
- Database Schema Reference: Explore our SchemaSpy ER Diagrams
Forest Client Wiki | GitHub Repository
- Architecture Overview
- Frontend Architecture
- Frontend Structure
- Backend Architecture
- Backend Structure
- Legacy Architecture
- Processor Architecture
- Data Model
- Development Overview
- Local Setup & Docker
- Frontend Setup
- Backend Setup
- Project Conventions
- Frontend Structure Guidelines