-
Notifications
You must be signed in to change notification settings - Fork 64
-
Notifications
You must be signed in to change notification settings - Fork 64
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
Problem with SimpleREST ContainerMode #162
Comments
I think you are doing nothing wrong. |
OK, everything looks correct, so most likely a bug in Botium. |
Where i have to put debug settings? Using to run: |
just use "--verbose" command line switch |
`2018-12-19T09:16:10.225Z botium-cli Using Botium configuration file botium.rest.json 2018-12-19T09:16:10.462Z botium-cli-run ready reading convos (1), expanding convos ... 1..1 tests 1pass 0fail 12018-12-19T09:16:11.172Z botium-BaseContainer Cleanup rimrafing temp dir D:\botiumwork\Chatbot-20181219-111610-UxAbp |
one more question - what version are you using ? (botium-cli --version) |
nevermind, please take the latest botium-cli version, this should be fixed now. |
Any Update here ? |
Hello, tried changes from and received "TranscriptError: Error: general_flow-A7/Cell B8: bot says nothing" But once replaced line in SimpleRestContainer.json (line 165) |
@codeforequity-at , sorry for delayed response, does fix from previous message make sense? Could it be fixed in scope of this issue, or should I create new one? |
We recently applied a fix to botium-core which will make your code changes obsolete (in fact, it solved the same problem as your code, just without using the evil "eval" call. |
how can i track applied fix? how to know proper version? |
The fix is here:
check in your locale node_modules/botium-core - or remove the whole directory (and package-lock.json) and install again. |
verified with version 1.4.3, still reproducible.
|
I cannot add the code you posted to Botium, because it is a huge huge huge security leak - it would basically allow your chatbot server to execute any Javascript code on your test automation server, and I am pretty sure you don't want that ... |
Please find attached last verbose log I hope it will be helpful |
Thanks it is somehow helpful. There is nothing wrong with your configuration, the JSON content and the JSON path settings are correct, I validated everything in detail. This means that I currently now idea why in your environment the context is not correctly evaluated. What I can offer: if you could publish your localhost chatbot with ngrok and send me over the endpoint, I can use a debugger to reproduce and debug it. |
We are trying to test with botium our custom API to Watson chatbot.
For this we have used SIMPLEREST container mode.
botium.json
` "botium": {
"Capabilities": {
"PROJECTNAME": "Chatbot",
"CONTAINERMODE": "simplerest",
}`
Receiving an error:
As a solution we add code to SimpleRestContainer.js
Instead of code begin from line # 165
We began to use :
With this fix testing works for us.
Is this is an issue? or Should we use Simplerest in other way?
How we could handle serialization of body?
The text was updated successfully, but these errors were encountered: