You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I needed "smarter" KATT scenarios so I implemented a new step type that I call action. It allows you to write Erlang code as a step and it looks like this, tell me what you think:
Running this in the erlang shell:
katt:run("priv/test_action.apib", [{inparam, "invalue"}]).
POST /helloworld
> Accept: text/html
Hello {{<inparam}}
< 200
{
"param1":"{{>param1}}",
"param2":"{{>param2}}"
}
! erlang <<<
A = mymodule:dostuff("{{<param1}}"),
B = othermodule:dostuff("{{<param2}}"),
[{outparam1, A},{outparam2, B}].
>>>
POST {{<outparam1}}/{{<outparam2}}
< 200
The text was updated successfully, but these errors were encountered:
It is very similar but this one is more generic because it is not tied to a request. Code executed outside the context of a request makes it much cleaner IMHO.
Hi.
I needed "smarter" KATT scenarios so I implemented a new step type that I call action. It allows you to write Erlang code as a step and it looks like this, tell me what you think:
Running this in the erlang shell:
katt:run("priv/test_action.apib", [{inparam, "invalue"}]).
The text was updated successfully, but these errors were encountered: