...
| Page Properties | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Overrides/Supersedes
When applicable, provide links to all DRs that this DR overrides or supersedes
RFC
Provide links to all relevant RFC's
Stakeholders
@mention individual(s) who has vested interest in the DR. This helps us to identify who needs to be aware of the decisionThis decision was migrated from the Tech Leads Decision Log as part of a consolidation process. The original decision record can be found here.
RFC
N/A
Stakeholders
All Backend Developers
Contributors
Approvers
List TC members voted to approve the change
Background/Context
...
This decision was made by the Tech Leads group prior to the adoption of current decision making processes within the FOLIO project.
Background/Context
Some bugs can only be discovered by integrating modules together. It is challenging to identify these on an ongoing basis.Some integration tests were already implemented. They use Postman collections. They are simple to write but harder to maintain. It can be challenging to express more complex scenarios. Many of which were contributed by ThunderJet team.
Assumptions
List all assumptions that were made when making the decision
Constraints
List any constraints that lead us to make a certain decision
Rationale
Document the thought process, list reasons that lead to the final decisionN/A
Rationale
ThunderJet teams has considered a range of tools and recommend Karate tool.
No alternative proposals has been submitted therefore Karate framework is preferred method for creating API integration tests in 2020.
Decision
Use Karate test framework for writing integration tests
Implications
- Pros
- Provide a link to RFC when applicableN/A
- Cons
- Provide a link to RFC when applicableN/A
Other Related Resources