-
Notifications
You must be signed in to change notification settings - Fork 552
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
feat: add test suite for the cli tests #3715
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
utACK
func (s *IntegrationTestSuite) SetupTest() { | ||
s.T().Log("setting up test") | ||
s.cfg = network.DefaultConfig() | ||
} | ||
|
||
func (s *IntegrationTestSuite) SetupSuite() { | ||
s.T().Log("setting up integration test suite") | ||
s.cfg = network.DefaultConfig() | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure but wouldn't it make sense to set the config per test and remove the config initialization from the suite?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We are setting the config per test, but since we have a global config we are resetting the config for each test
Description
The mutex lock into the package
cosmos-sdk/testutil/network/network
is blocking the CLI tests into a scaffolded ChainSolution
Move to the suite test
This PR also speeds up the chain and Ignite integration tests