-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reports doesn't log requests when call a feature using javascript #965
Comments
@sromeu-ob I'm marking this is a won't fix, because there is a limit to what we support and I still don't understand the weird nesting you are trying. I'll like your help to identify what is and what isn't possible. and if you want you can create a PR for the readme personally I highly discourage nested calls, especially JS. if you want some history and a related discussion, and WHY - see this: #722 and finally if you can contribute a fix, nothing like it :) |
👍 😉 |
sorry @sormuras I tagged you by mistake and then edited :) |
this was pending for a long time and I think with a thread-local approach it is done also made embedding more fool-proof especially in driver / robot call edge cases
@sromeu-ob if you have time can you test that the fix in the |
0.9.6 released |
HI,
I realised that when you call a feature file or an specific scenario using a javascript function, all requests made in the called feature are not logged to the html reports.
On the other hand, if I call a feature file or scenario using the "call read" step,, it works fine and all requests are printed in the report.
Peter, I have updated the previous sample project in order to create a flow that make sense.
Thanks!
karate-basic.zip
The text was updated successfully, but these errors were encountered: