-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
INFRA-505: Move integration tests to unit tests #6530
INFRA-505: Move integration tests to unit tests #6530
Conversation
node/src/test/kotlin/net/corda/node/internal/AbstractNodeKeystoreCheckTest.kt
Outdated
Show resolved
Hide resolved
node/src/test/kotlin/net/corda/node/internal/AbstractNodeKeystoreCheckTest.kt
Outdated
Show resolved
Hide resolved
node/src/main/kotlin/net/corda/node/internal/NodeKeyStoreUtilities.kt
Outdated
Show resolved
Hide resolved
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.
Thank you, looks good.
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.
I have one more thing, sorry for chaotic comments.
Newly added fine-gran tests and small re-factoring are fine. But how do we conceptually make sure that initKeyStores() is properly called on the node start after removal of integration tests?
@rnicoll , what do you think?
|
…sts-to-unit-tests
So it's a two part answer here; on the one hand, I think the dozens of tests which spin up full nodes then interact with their node info will cover this. The other part, however, is that I would look to unit tests to stop accidental errors creeping in, rather than model how the code is written currently. Having a unit test for |
…sts-to-unit-tests
Move two integration tests to a few unit tests.