QA & Automation¶
TL;DR — QAs write Selenium-based automation tests that run daily on the RC environment for both E2E frontend flows and API coverage. Per-repo automated testing varies: frontend test coverage is limited; microservices typically include unit tests.
Overview¶
Quality assurance combines QA-owned automated suites (one QA per feature team) with per-repo tests written by developers.
QA automation suite¶
- Framework: Selenium.
- Schedule: daily runs.
- Environment: RC — see aws-infrastructure.md.
- Coverage:
- Frontend E2E flows — validates investor journeys and issuer flows end-to-end.
- API testing — scope is being expanded; full coverage is not yet documented.
Testing state by tier¶
| Tier | State | Notes |
|---|---|---|
| Microservices (backend) | Unit tests exist in most services. | Coverage enforced via Code Insights thresholds (see code-insights.md for defaults). |
| Frontends / MicroFrontends | Test coverage is limited. | See frontend-architecture.md. |
| Integration | Handled by the QA Selenium suite on RC. | Runs daily, not per-PR. |
Implications for development¶
CI vs. production readiness
CI does not run the full integration/QA suite per PR — integration regressions are detected by the daily QA runs on RC, not at merge time.
See also¶
- Frontend Architecture — Detail on the frontend testing gap.
- Code Insights & Coverage — How coverage is enforced at PR time.
- AWS Infrastructure — Why RC matters (daily automation target).