Closed combsco closed 7 years ago
I'm sorry, I never used ESpec before. I'll try it this weekend and respond you soon.
Hi @combsco I guess you were talking about https://github.com/combsco/auberge so I test it directly.
Your API returned {"updated_at":"2017-01-23T06:05:44.000000Z","phone_num":"5555555555","last_name":"Doe","inserted_at":"2017-01-23T06:05:44.000000Z","id":"823fe148-f1d1-4e08-93f5-260a819eaf50","first_name":"John","email":"john.doe@gmail.com"}
Your expected data is {"updated_at":null,"phone_num":"5555555555","last_name":"Doe","inserted_at":null,"id":2,"first_name":"John","email":"john.doe@gmail.com"}
the inserted_at
and updated_at
are not the same, so test failed.
Maru depends on Plug and Plug send it. I'll look into it to find a solution, just ignore it for now.
Testing with straight plug is in the plan, I'll make sure you won't change too much code to use it after it released.
Thank you for using Maru ❤️
Hey @falood
Thanks for looking into it. Yeah I haven't updated my only test in Auberge as I've changed some stuff since so that test was bound to fail.
But yeah I can just ignore the unhandled message I just wondered if it was supposed to go somewhere and how ExUnit handles it.
Thanks for developing Maru!
Maybe that's what I should check.
from here, I find plug process {:plug_conn, :sent}
message itself, so I guess I should do the same thing for maru.
I'll post it here after I find the correct way to do this 🙂
Just like what plug
do, receive these kind of message myself.
Leave me a line if there's any other question 🙂
Anyway I can suppress Maru.Test from doing that or would it be better to test with straight Plug?
Output Log