Skip to content

e2e: Group tests better for easy developer onboarding #8363

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
DeshErBojhaa opened this issue May 9, 2025 · 0 comments
Open

e2e: Group tests better for easy developer onboarding #8363

DeshErBojhaa opened this issue May 9, 2025 · 0 comments
Assignees

Comments

@DeshErBojhaa
Copy link
Contributor

We can consider running/exposing a subset of tests from the Makefile.

Upgrade e2e tests require extra setup in ibc-go-e2e-config.yaml. Which is not obvious for someone new to the repo. Also upgrade tests are excluded in the default CI workflow.

jobs:
  e2e:
    with:
      test-exclusions: 'TestUpgradeTestSuite,TestTransferTestSuite,TestAuthzTransferTestSuite,TestTransferTestSuiteSendReceive,TestTransferTestSuiteSendEnabled,TestTransferLocalhostTestSuite,TestConnectionTestSuite,TestInterchainAccountsGovTestSuite'

Given all this, we should figure out how to organize/grop tests for a better developer obboarding.

Possible considerations:

  • More clear documentation
  • More explicit fail msg
  • New make command that only shows the functionality tests. And another make command that shows all tests.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants