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

ledger-api-test tool: better test coverage #146

Open
ghost opened this issue Mar 28, 2019 · 2 comments

Comments

@ghost
Copy link

commented Mar 28, 2019

Todo's for further iterations on testing the conformance of a Ledger API server

Coverage improvements:

  • port all black box tests from other integration tests into the tool to extend the test coverage
  • ensure semantic tester can check multi-participant workflows (requires to provide it with a topology configuration stating what party is hosted at what Ledger API)
  • elicit error paths (e.g. submitting an ill-typed command)
  • validate that the semantic tester is precise wrt to returned transaction trees (i.e., also checks that not too much data is shown)
  • cover #786

Features:

  • remove reset requirement using the <uuid> prefix for parties choosing a new for every test

Quality:

  • test the semantic tester (i.e., ensure it actually does find problems in the implementation)
@meiersi-da

This comment has been minimized.

Copy link
Contributor

commented Apr 24, 2019

@gleber-da : I've just found this pre-existing ticket for additional tests that we would like to have. Many will probably be covered by the remaining ledger integration tests of the Sandbox code. I've assigned this ticket to you so you can coordinate and update accordingly with the knowledge you gain from the investigation into the remaining ledger integration tests of the Sandbox code.

@meiersi-da meiersi-da changed the title Semantic tests - further iterations ledger-api-test tool: Semantic tests - further iterations Apr 24, 2019

@gleber-da

This comment has been minimized.

Copy link
Contributor

commented Apr 24, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.