and when it starts it sends a message to itself, which does some complicated logic of sending messages to someone else and having responses back
I am not sure if it's easy to comprehend
check this one for instance: WhenWidgetConfigurationProviderFailsShouldRetry
or this one: InitWidgetManagerActorWithSeveralWidgets
Maxim Cherednik
@maxcherednik
so the idea is that you send a message to the child actor and you should be prepared that it will never reply....
in this case you need to have backup logic of retry...
do you follow? :)
_
Daniel Söderberg
@raskolnikoov
yes I follow
Maxim Cherednik
@maxcherednik
for instance in my WidgetManagerActor I am injecting the actor, so it's not exactly a child.... but I need it this way.... in you case you can have a Props param from the constructor....
in the prod code - you set the real child actor's props, in the test code you have a props of the TestProbe
Daniel Söderberg
@raskolnikoov
yes.. but I will have to rewrite my test case for this. Thanks for the help! :)
Maxim Cherednik
@maxcherednik
you will probably need to rewrite lots of things :)
but anyhow... try it... other than this, I don't know how to handle this
Daniel Söderberg
@raskolnikoov
I talked to Roger Johansson about this now and he answered that it's not possible to do my test case.
Maxim Cherednik
@maxcherednik
yeah - like you described - not possible...
Aaron Stannard
@Aaronontheweb
@Rattenkrieg I haven't seen any examples of this being needed in practice
but with your changes to the MNTR in #2502
is it still possible to give one node amongst the others in the spec its own configuration?
I.E. if I wanted to run a test that gave one node a different configuration from the others?
I kind of think this is YAGNI to some extent, but still - that's a capability we had before that I would like to preserve in some capacity