Our testing strategy for Codex is pretty ad-hoc, so having more of a continuous workflow would help us scale and streamline our day-to-day processes.
Considerations:
Output:
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Duplicate | • STH | T302348 <Platform Initiative> Release Codex in Beta (Limited Production Release) | |||
| Invalid | None | T302025 Upgrade Codex to Beta version | |||
| Invalid | None | T302038 [Epic] Define testing and QA strategy for Codex | |||
| Resolved | Catrope | T308291 Define test cases for Codex functional testing |
A document was created to details the test cases that can be carried out on components that have been currently developed. Further components that would be developed would have their test cases documented here. I believe this suffices for this task.