Skip to end of banner
Go to start of banner

DR-000011 - Karate test framework for Integration Tests

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Current »

Submitted Date

 

Approved Date

 

StatusACCEPTED
ImpactLOW

 

Overrides/Supersedes 

This 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

Anton Emelianov (Deactivated) 

Approvers

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

N/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
    • N/A
  • Cons
    • N/A

Other Related Resources

  • No labels