Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 16:24
    IgorFedchenko commented #3973
  • 16:11
    IgorFedchenko commented #3973
  • 16:09
    IgorFedchenko commented #3973
  • 16:08
    IgorFedchenko synchronize #3973
  • 16:04
    IgorFedchenko commented #3973
  • 16:04
    IgorFedchenko synchronize #3973
  • 15:26
    IgorFedchenko synchronize #3973
  • 15:20
    IgorFedchenko synchronize #3973
  • 14:54
    IgorFedchenko synchronize #3973
  • 14:49
    IgorFedchenko synchronize #3973
  • Oct 22 21:12
    Aaronontheweb commented #4001
  • Oct 22 21:11

    Aaronontheweb on dev

    Added missing Persistence Testi… (compare)

  • Oct 22 21:11
    Aaronontheweb closed #4001
  • Oct 22 20:59
    sean-gilliam commented #3889
  • Oct 22 20:59
    sean-gilliam opened #4001
  • Oct 22 16:07
    spankr commented #3921
  • Oct 22 15:55
    Aaronontheweb labeled #3765
  • Oct 22 15:54
    Aaronontheweb labeled #3765
  • Oct 22 15:54
    Aaronontheweb milestoned #3765
  • Oct 22 15:53
    Aaronontheweb closed #3902
Maxim Cherednik
@maxcherednik
basically what you are testing is simple request response, hence the very first example from that blog should work...
another thing - when you actually hit the storage - it's not exactly a unit test
how about you replace all the storage actors and try it again ?
cause from what you describe - it should work
if you do everything else right, the only reason to fail is wrong persistence configuration
Daniel Söderberg
@raskolnikoov
no it dosent work.. :(
tried to do it with a simple A and B actor test... I called my A actor that calls B actor and returns to A actor... the return message to my A actor dosent every occur in my ExpectMsg
:/
I want to catch the Recive<MyMessage>
Maxim Cherednik
@maxcherednik
hm...
Daniel Söderberg
@raskolnikoov
im trying to test a actor that never returns a message
I just want to check that it gets a certain message
Maxim Cherednik
@maxcherednik
then there is something wrong in general
what about the very simple scenario ?
Daniel Söderberg
@raskolnikoov
that dosent work
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? :)