-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Unknown
-
None
-
Affects Version/s: None
-
Component/s: Testing
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Use Case
As a... (who is this for)
I want... (what is the desired change)
So that... (why is the change desired)
This is a new AI Integration. We want CI running regularly.
User Experience
- What is the desired/expected outcome for the user once this ticket is implemented?
- If bug: What is the number of impacted customers? How severe is the impact? Is anyone blocked or broken?
Confidence that our integration is working as intended.
Dependencies
- upstream and/or downstream requirements and timelines to bear in mind.
Currently there is a community implementation. We can create this concurrently with improving on it.
Risks/Unknowns
- What could go wrong while implementing this change? (e.g., performance, inadvertent behavioral changes in adjacent functionality, existing tech debt, etc)
- Is there an opportunity for better cross-driver alignment or testing in this area?
- Is there an opportunity to improve existing documentation on this subject?
We may have to decide on any breaking changes.
Acceptance Criteria
Implementation Requirements
- functional reqs, potential snafus to avoid, performance targets, etc
Might need a review from dbx-node team.
Testing Requirements
- unit test, spec test sync, etc
This itself is CI. ![]()
Documentation Requirements
- DOCSP ticket, API docs, etc
Follow Up Requirements
- additional tickets to file, required releases, etc
- if node behavior differs/will differ from other drivers, confirm with dbx devs what standard to aim for and what plan, if any, exists to reconcile the diverging behavior moving forward
- is related to
-
NODE-7556 Spike: Audit MongoDB Adapter for Production Readiness
-
- In Progress
-