-
Type: Epic
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Component/s: CRUD
-
None
-
To Do
-
Comprehensive Crud Spec Tests
-
Needed
Summary
The lack of comprehensive CRUD spec tests makes it harder than it should be to write a new driver (e.g. pure Swift driver). We could likely generate tests by using APM against an existing driver and validating them against other existing drivers.
Motivation
This was discussed at Drivers QP Prep for FY22Q1 and endorsed by many of the drivers leads. The lack of tests is causing engineering maintenance pain and should be addressed.
Cast of Characters
Engineering Lead:
Document Author:
POCers:
Product Owner:
Program Manager:
Stakeholders:
Documentation
[Scope Document|some.url]
[Technical Design Document|some.url]
- is duplicated by
-
DRIVERS-715 Exhaustive CRUD spec testing
- Development Complete
- is related to
-
DRIVERS-1525 Migrate all Spec Tests to The Unified Test Runner
- In Progress
- related to
-
DRIVERS-2052 Add APM tests for findAndModify
- Backlog