-
Notifications
You must be signed in to change notification settings - Fork 75
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
[ETCM-126] split JsonRpcControllerSpec #734
Conversation
…r and simplify tests using them
…erSpec into JsonRpcControllerPersonalSpec
…ec to JsonRpcCOntrollerEthTransactionSpec
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.
Nice job. One doubt only
val version = Config.clientVersion | ||
val blockGenerator = mock[EthashBlockGenerator] | ||
|
||
override implicit lazy val system = ActorSystem("JsonRpcControllerSpec_System") |
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.
Do we need to create ActorSystem for each test?
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.
This.
I'd say it's preferrable to use akka's TestKit
on suite level and use there WithActorSystemShutdown
trait.
Benefits are as follows:
- Creating and shutting down systems is quite expensive operation.
- Actors of any kind are created per spec anyways so lack of isolation is not an issue I think
- In other project we had real problems with tests due to leaking running actor systems
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.
How about merging this PR and fix the unnecessary spawning actor system in a separate one.
There is a pretty complex wiring using cake pattern (actor system that comes from ActorSystemBuilder
(via StdTestConsensusBuilder
via ScenarioSetup
via EphemBlockchainTestSetup
and ActorSystemBilder is required in StdLedgerBuilder
via self type). I need some time to figure out how to do this.
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.
Sounds good to me. And such task/PR could be extended to making sure actor system is properly closed in all tests.
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.
PR for this change: #751
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.
Overall looks good to me!
Description
JsonRpcControllerSpec file contained around 2000 lines of code. This is hard to maintain. Context for this PR: #726 (comment)
Proposed Solution
Split it into tests related to:
JsonRpcControllerPersonalSpec
personal_XYZJsonRpcControllerEthTransactionSpec
related to eth transaction requestsJsonRpcControllerEthSpec
other eth requestsJsonRpcControllerSpec
other requestsBefore split there were utility function extracted that simplify creating requests and creating JsonRpcService:
newJsonRpcController
,newJsonRpcRequest
in 53283b7Important Changes Introduced
Testing