testing-standards

Standardized testing practices apply across unit, integration, and end-to-end scenarios to guide development and quality assurance. They specify required documentation, naming conventions, Arrange-Act-Assert structure, and deterministic mock data strategies to improve code quality and reliability.

Structure unit tests by separating each test into three distinct phases: arrange the required mock data and preconditions, act by executing the target method, and assert the expected outcomes. This standardized structure ensures tests remain readable and maintainable.

Best practices for deterministic mock data involve establishing consistent guidelines for generating and managing test fixtures. This prevents flaky tests by ensuring integration testing scenarios produce reliable, repeatable results independent of external system states.

Yes, these testing standards apply to both development and code review workflows. They guide teams when writing tests during development and provide review criteria during quality assurance to verify compliance with naming conventions and structural patterns.

Yes, the specified naming conventions, test structure patterns, and mock data strategies can be implemented directly into project templates. This allows teams to standardize testing conventions and baseline coverage plans immediately when kicking off a new project.