Issue with Injection in Predicate

[anu0123]

Hi

I am unable to inject any Javascript function inside the predicates of one of the stub.
In the request i have asked to match the Query under PredicateGenerators.

The function which i have written is very simple
"predicates": [
{
{ "deepEquals":
{
"query":
{"inject": "function(logger)
{logger.info('Inside injection';)}"
}}}
}
I am not able to see any information on logs.
I have allowed Injection on mountebank startup by
mb --allowInjection.

Can anyone suggest anything ? Or if any changes has to be made ?

[bbyars]

Hi there,
The inject predicate looks unlike the other predicates because it needs
access to the entire request and therefore has to be at the top level.
Your example would need to look something like this:

"predicates": [
{
"inject": "function(request, logger) { logger.info('Inside injection');
logger.info(JSON.stringify(request, null, 4)); }"
}
]

The second log statement will show you what the request looks like, and you
can use that to do whatever tests you need. Let me know if that's still
confusing, happy to help you sort it out.
-Brandon

On Fri, Apr 10, 2015 at 12:49 PM, anu0123 notifications@github.com wrote:

Hi

I am unable to inject any Javascript function inside the predicates of one
of the stub.
In the request i have asked to match the Query under PredicateGenerators.

The function which i have written is very simple
"predicates": [
{

{ "deepEquals":
{
"query":
{"inject": "function(logger)
{logger.info('Inside injection';)}"
}}}
}
I am not able to see any information on logs.
I have allowed Injection on mountebank startup by
mb --allowInjection.

Can anyone suggest anything ? Or if any changes has to be made ?

—
Reply to this email directly or view it on GitHub
#63.

[anu0123]

I am injecting this function in a response which is captured after loading a request onto MounteBank but still it doesn't work.
I had one other question too. Which all predicates can we use besides matches in PredicateGenerators? Any other used with proper syntax throws errors.
Ex I am using : {
"port": 7575,
"protocol": "http",
"stubs": [
{
"responses": [
{
"proxy": {
"to": "http://www.orgin-server",
"mode": "proxyOnce",
"predicateGenerators": [
{
"or": [
{
"matches": {
"query": true
}
},
{
"contains": {
"query": "lp"
}
}
]
}
]
}
}
]
}
]
}

[bbyars]

Hi there,
Responses inline:

I am injecting this function in a response which is captured after loading

a request onto MounteBank but still it doesn't work.

Sorry you're having trouble. Can you send the full imposter JSON you're
sending so I can troubleshoot?

I had one other question too. Which all predicates can we use besides

matches in PredicateGenerators? Any other used with proper syntax throws
errors.

The predicateGenerators objects only accept matches. You can augment them
with caseSensitive and except, but you can't use them to create a contains
predicate, for example.

Ex I am using : {
"port": 7575,
"protocol": "http",
"stubs": [
{
"responses": [
{
"proxy": {
"to": "http://www.orgin-server",
"mode": "proxyOnce",
"predicateGenerators": [
{
"or": [
{
"matches": {
"query": true
}
},
{
"contains": {
"query": "lp"
}
}
]
}
]
}
}
]
}
]
}

—
Reply to this email directly or view it on GitHub
#63 (comment).

[bbyars]

Yes. The decorate behavior <http://www.mbtest.org/docs/api/behaviors#behavior-decorate> accepts both the request and response as parameters. You can return the modified response from the function. See the linked to page for examples. -Brandon

…

On Sat, Oct 27, 2018 at 12:31 AM RoyalGunjan007 ***@***.***> wrote: Is there a way to read response file inside decorate and modify it as per use? — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#63 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAESvyYeDpyDEaEUZckaroRTsrEtZtwvks5uo--rgaJpZM4D-MU4> .