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

Create guidelines and tutorials on how to use different type of testing frameworks #1335

Open
6 tasks
Tracked by #1331
MSalopek opened this issue Sep 28, 2023 · 3 comments
Open
6 tasks
Tracked by #1331
Assignees
Labels
scope: docs Improvements or additions to documentation scope: testing Code review, testing, making sure the code is following the specification. type: tech-debt Slows down development in the long run

Comments

@MSalopek
Copy link
Contributor

MSalopek commented Sep 28, 2023

This issue is tracking progress on creating guidelines and tutorials and testing that do not relate to e2e tests.

Please list any questions you want answered in this issue so they can get the necessary attention:

  • mock generation
  • scoping unittests
  • scoping integration tests
  • working with ibc-go/testing
  • overriding ibc-go/testing
  • streaming data from the test database
@MSalopek MSalopek changed the title tutorials on how to use different type of testing Create guidelines and tutorials on how to use different type of testing frameworks Sep 28, 2023
@MSalopek MSalopek self-assigned this Sep 28, 2023
@MSalopek MSalopek added scope: docs Improvements or additions to documentation scope: testing Code review, testing, making sure the code is following the specification. type: tech-debt Slows down development in the long run labels Sep 28, 2023
@shaspitz
Copy link
Contributor

shaspitz commented Oct 4, 2023

This issue should build off the ideas already in https://github.com/cosmos/interchain-security/blob/main/docs/old/testing.md. I can take a crack at some of the ideas this week

@shaspitz
Copy link
Contributor

shaspitz commented Oct 4, 2023

Note that #625 should be addressed in the docs. It's not neccessary to refactor a bunch of UTs, but there should be a guideline of how unit tests should be written.

UTs should be as simple and blackbox as possible, without sneaking in patterns of property based testing

@shaspitz
Copy link
Contributor

shaspitz commented Oct 5, 2023

Here's a start on closing this issue #1342

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
scope: docs Improvements or additions to documentation scope: testing Code review, testing, making sure the code is following the specification. type: tech-debt Slows down development in the long run
Projects
Status: 📥 F2: Todo
Development

No branches or pull requests

2 participants