...

1. What is being done here:
   1. Making sure the visual representation of the bot looks good
   2. Looking for anything that looks out of place.
2. Steps
   1. Go to the Designer view
      1. 
   2. This process is more "look around and see what looks off". Being familiar with the bot logic and how the bot looks in the Designer view will greatly help.
   3. Click the Run button at walk through the bot watching how each part of the bot flows.
      1. 
   4. Answer questions using the Web Chat box
      1. 
   5. If the bot is small enough, use the Watch window to follow the bots progress. Items here can be expanded to she values of parameter as they are selected. i.e. In the image below, Male was selected for question showing in Web Chat and the selections shows as the value for the variable "gender" in the Watch window.

      1. Image ModifiedNOTE:

         Info
         If the bot is too large and the Watch window shows the error "Data is too large to be shown in the debugger", there is a work-around. The areas of the bot not being tested can be deleted. Doing this can make the bot small enough to test specific areas.

         
         

         Warning
         This should only be done in a non-production environment and using a copy that will not cause problems if lost.

         
         

   6. If the bot is small enough, use the Immediate window to find the value of a specific variable. i.e. In the image below, typing "scenario.gender" and hitting the Evaluate button returns the current value of the "gender" variable.
      1. 

Checking the pathways

1. What is being done here:
   1. Walking through all the different pathway using the front-end
   2. Checking for correct flow of questions
   3. Checking for correct messaging
   4. Checking that questions with checkboxes work as expected
2. Steps
   1. Open a non-production version of the bot in a browser
   2. Walk through the bot and do the following:
      1. answer questions and check for correct flow
      2. check and uncheck boxes making sure they work as expected
      3. look at questions to make sure they are formatted correctly
      4. look at the message returned at the end making sure they are correct and formatted correctly
   3. Use the bot documentation to track your progress. If any issues are found, provide the question number or message number or message ID or screen shot to the developer so they know exactly where the issue is located. 
   4. Check the database connected to the bot to verify the data being collected it correct. If the review of the backend code went well, hopefully there are no issues here.