Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Jan 28 22:17
    Aaronontheweb edited #4152
  • Jan 28 22:16
    Aaronontheweb milestoned #2750
  • Jan 28 22:16
    Aaronontheweb demilestoned #2750
  • Jan 28 22:15
    Aaronontheweb milestoned #4007
  • Jan 28 22:15
    Aaronontheweb demilestoned #4007
  • Jan 28 22:14
    Aaronontheweb synchronize #4086
  • Jan 28 21:49

    Aaronontheweb on 1.4.0-beta4

    (compare)

  • Jan 28 21:47

    Aaronontheweb on dev

    V1.4.0 beta4 release notes (#41… (compare)

  • Jan 28 21:47
    Aaronontheweb closed #4174
  • Jan 28 21:45

    Aaronontheweb on dev

    modified build script so if the… (compare)

  • Jan 28 21:45
    Aaronontheweb closed #4175
  • Jan 28 21:42
    Aaronontheweb labeled #4175
  • Jan 28 21:42
    Aaronontheweb opened #4175
  • Jan 28 21:02
    Aaronontheweb synchronize #4174
  • Jan 28 21:02
    Aaronontheweb opened #4174
  • Jan 28 20:47
    Aaronontheweb demilestoned #4096
  • Jan 28 20:47
    Aaronontheweb edited #4096
  • Jan 28 20:25

    Aaronontheweb on dev

    added real header to Akka.Remot… (compare)

  • Jan 28 20:25
    Aaronontheweb closed #4173
  • Jan 28 20:20
    Aaronontheweb labeled #4173
Maxim Cherednik
@maxcherednik
like one actor - you send ping, it responds pong and you expect this pong on the test actor ?
Daniel Söderberg
@raskolnikoov
let me upload an example
how can I test this example with valid result :)
Maxim Cherednik
@maxcherednik
ok, like I thought it's not that simple then

so when you are here:

Receive<MessageFromB>(msg =>
{
//test if this happends in here!
});

you don't send it back to the original caller, right ?
Daniel Söderberg
@raskolnikoov
no that's the end
so I would like to check that this end occurs
Maxim Cherednik
@maxcherednik
in this case you can't test this
Daniel Söderberg
@raskolnikoov
daaaaaaaaam
:P
that's something you want tested :)
Maxim Cherednik
@maxcherednik
from the same article I sent
"How do I test a parent/child relationship?"
check it
actually it's not exactly this...
nevermind
I think you should test something else
give me a sec
Daniel Söderberg
@raskolnikoov
hehe and get a cup of coffee :)
brbr!
Daniel Söderberg
@raskolnikoov
back @maxcherednik
Maxim Cherednik
@maxcherednik
have a look at this guy
in there I have a similar situation
I've got this main actor: WidgetManagerActor
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
in case you missed it, YAGNI