Testing the Chatbot:
- Lets attempt to create a brand new pet in our pet retailer. I simply put the question as “add a pet” and it was rapidly in a position to perceive what are the required parameters to create a pet. So the bot requested me one after the other to enter the identify after which the id for our new pet. As soon as it obtained all of the required data, it created the pet.
2. Let’s attempt to get the knowledge for our newly created pet. After I ask “get pet”, it understood that there’s not API to get all pets and therefore requested me for an id. As soon as the id is entered, the chatbot was in a position to fetch the knowledge for the pet we simply now created.
3. Let’s add yet another pet. When queried for “add a pet”, it requested for the identify, then id after which lastly the standing. Discover the way it gave me the choices for standing (obtainable, pending or bought). It is because these are the choices talked about within the YAML file for the standing area.
4. Let’s attempt to get the brand new pet that we created. The Chatbot will get the whole data when the id is entered.
5. Now allow us to attempt to replace the pet and see if the bot is ready to deal with it. So after I question “replace pet”, it asks for the id, after which asks what area i have to replace, is it identify or standing. So after I enter “standing is bought”, it updates that and offers the response for the profitable standing replace.
6. To be really positive if the worth is up to date in backend or not, I attempted to get the pet infomation. However this time, within the first question itself i’ve the id and did a question as “get pet 123”. This time the Chatbot obtained the id and didn’t ask once more for the id. Within the very subsequent step, it has come again with the response saying the pet with id 123 is bought.
7. Lastly, lets now attempt to delete the pet. After I question “delete pet”, the Chatbot asks me for the id, and when the id is entered it deletes that entry for pet with id 123.
As seen above, We had been in a position to work together with our API, carry out CRUD operations (Create, Learn, Replace, Delete) by means of the Chatbot which required no coaching, no coding!!