News for hackers. Stuff that matters.
Re:WireMock by mahesh_rm on Friday September 07, 2018 @05:37PM (#17937869)
"Development and QA was done against the mocks because the real target system did not exist yet."

Wouldn't this be frontend discovery/development, rather than frontend testing? In this case, I recognize the tool can be useful.

"For example, what if the web service we hit returns a 500 error?"

Isn't this what development and staging environments are for? Not trying to be polemic/destructive, I just see building and maintaining mock api templates as a further overhead, when specific backend behavior can be simulated in an alternative deployment environment once a backend is in fact there. But maybe I don't fully understand the constraints posed by workflows other than mine! :-)

Re:WireMock by Consultant32452 on Friday September 07, 2018 @09:38PM (#17938901)
You may not have any control whatsoever over the backend. You may not even have the ability to create data scenarios you want to test. Creating large/complex data scenarios is almost always more time intense than creating a mock. Honestly, creating simple data scenarios is almost always more time intense than creating a mock.