Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open Payments: E2E conformance testing #18

Open
matdehaast opened this issue Oct 10, 2022 · 1 comment
Open

Open Payments: E2E conformance testing #18

matdehaast opened this issue Oct 10, 2022 · 1 comment
Assignees

Comments

@matdehaast
Copy link

matdehaast commented Oct 10, 2022

Summary

The goal of this issue is to have full E2E conformance tests for the open payment apis, where we can ensure that an implementation is conformant to the API spec.

This is still being fleshed out and awaiting a full proposal from @omertoast

Intended Outcomes

  • Pre-defined config files to standardize testing cases
  • Modular test creation
  • Automate tests using CI/CD
  • Have scenarios (test modules) consisting of multiple requests and responses to simulate a real-life scenario.

How will it work?

  • We are planning to use conformance suite as the primary testing tool. It's created and used by OpenID to test OpenID Connect and higher-level specs like FAPI. We have to create test modules for each case we want to test. After having a Rafiki instance up and seeded with demo values, we can run the conformance suite against it.

Links

@matdehaast matdehaast moved this to Future in High Level Roadmap Oct 10, 2022
@omertoast omertoast self-assigned this Oct 10, 2022
@omertoast omertoast moved this from Future to Q4 2022 in High Level Roadmap Oct 19, 2022
@omertoast
Copy link

I created a fork of the conformance suite and a few scenarios you can try to run.

@AlexLakatos AlexLakatos moved this from Q4 2022 to Q1 2023 in High Level Roadmap Jan 30, 2023
@AlexLakatos AlexLakatos moved this from Q1 2023 to Q2 2022 in High Level Roadmap Mar 27, 2023
@AlexLakatos AlexLakatos moved this from Q2 2022 to Q3 2022 in High Level Roadmap Apr 3, 2023
@sabineschaller sabineschaller moved this from Q3 2023 to Q4 2023 in High Level Roadmap Oct 3, 2023
@AlexLakatos AlexLakatos moved this from Q4 2023 to Q1 2024 in High Level Roadmap Oct 31, 2023
@sabineschaller sabineschaller moved this from Q1 2024 to Future in High Level Roadmap Jan 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Future
Development

No branches or pull requests

3 participants