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

Use only public APIs in Go end-to-end tests #207

Open
bestbeforetoday opened this issue Sep 20, 2024 · 0 comments
Open

Use only public APIs in Go end-to-end tests #207

bestbeforetoday opened this issue Sep 20, 2024 · 0 comments

Comments

@bestbeforetoday
Copy link
Member

bestbeforetoday commented Sep 20, 2024

As a Go contributor
I want the end-to-end tests to be implemented using only public APIs
So that I can ensure that the fabric-admin-sdk implementation is usable by consuming Go modules

The current end-to-end tests (in the test package) are part of the fabric-admin-sdk module and make use of internal packages for their implementation. These tests should ensure that the fabric-admin-sdk module provides end-to-end capability for consuming Go modules. One option to ensuring this is for the end-to-end tests to be defined in their own module so that they accurately reflect the experience of a consuming Go module, although this is not strictly necessary.

This change will require some rework of the end-to-end tests (and possibly the fabric-admin-sdk API) to implement the required functionality without accessing internal packages.

@bestbeforetoday bestbeforetoday changed the title Define a separate module for Go end-to-end tests Use only public APIs in Go end-to-end tests Sep 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant