aws-samples / amazon-lex-bot-test

Script to test an Amazon Lex bot using the Amazon Lex Runtime API.
MIT No Attribution
12 stars 14 forks source link

NotFoundException thrown for BotAlias name #1

Open vijayasankar opened 6 years ago

vijayasankar commented 6 years ago

Hi,

I used the teslexbot.js file from here to test our chatbot with modified tests in json file. But I get the Notfoundexception.

-----------------------test.json file below---------------------------------------------

{ "name": "KotahiBot-main", "description": "Regression tests for the Kotahi bot", "botName": "KotahiChatbot_Redo", "botAlias": "BETA", "waitBetweenRequestsMillis": 0, "sequences": [{ "name": "Hello_Kotahi", "description": "Greetings from Kotahi Chatbot", "sequence": [{ "utterance": "Hi", "postConditions": { "message": ["Hi! I'm your Kotahi chatbotassistant!"] } }, { "utterance": "where is my container", "postConditions": { "message": ["Sure! What is your case number\?"] } }, { "utterance": "00000102", "postConditions": { "message": ["I'm sorry. Unexpected problem occurred while I was searching for your case. Please call our service center."] } } ] }] } -----------------------------See the error log here..--------------------------------

$ node testlexbot.js test/test1.json I Running test cases from test/test1.json for KotahiChatbot_Redo:TERMINATOR - KotahiBot-main I Test sequence 1 / 1 - Hello_Kotahi botAlias: TERMINATOR

vijayasankar commented 6 years ago

Bot name : KotahiChatbot_Redo Aliases : BETA

TERMINATOR

TEST

nhira commented 6 years ago

I'm a little confused here... does test1.json (which is what you seem to be using in the command line) refer to BETA or TERMINATOR? Perhaps the easiest way to confirm this would be to use the CLI to invoke post-text to confirm that the alias you're hoping to use is accessible. aws lex-runtime post-text --bot-name ...

Hope this helps.

unnikrishnan-anil commented 4 years ago

any update on this? Facing the same issue.

EightRice commented 3 years ago

I'm getting this too. What's up?

bdhakad commented 2 years ago

anyone found fix or cause for this?

Lautaroef commented 1 year ago

I'm encountering the same issue

grand1nqu1s1tor commented 7 months ago

Any Solutions found?