Sushi Go Round Bot

1) Purpose:

The Purpose of this project was to create a bot that would play Sushi Go Round, learn the beginnings of Python and how to use Pycharm.This tutorial can be found at https://code.tutsplus.com/tutorials/how-to-build-a-python-bot-that-can-play-web-games--active-11117.I have put in multiple hours into this tutorial and as of right now everything is working like it is intended to. The code has minor differences from the tutorial in order to get my code to work on my machine.

2) Discussion of Solution:

A major problem I had was when I was trying to get the right sizes of the boxes to get the values of the sushi thought bubbles,  I followed the tutorial exactly to get the bottom right corner to create the box but that did not work on my machine. After double and triple checking my measurements for the top left corner in 2 different paint software, I looked at the images that printed out, I noticed that the images were only off by a few pixels and then I put the method of each seat into Main and then ran them individually and adjusted the images by 1 pixel in both the x and y-direction and found that instead of adding 63 to the x value and 16 to the y-value, if I added 62 to the x and 15 to the y then it worked. This was a minor problem that probably was caused by either a resolution difference between the machine used in the tutorial and my machine or due to a change in the way the website was laid out which is why the solution was so simple to fix but took me so long to realize that the pixels were only off by such a minute amount.  Below is the code and result of my code following what the tutorial said to do and then what I changed it to to get it to work as intended.

3) Testing Plan:

During the coding process, I learned that having a different zoom in Google Chrome or using a different size monitor will cause the bot to click on unintended spots on the website. After realizing this I always made sure to keep my laptop as my main display, have chrome’s zoom at 100%. While testing I also made sure to have print statements at every step when debugging and that printing out variable values and then comparing them to what they should be. Doing both of these help me speed up my debugging and made certain bugs easier to find and fix.  All measurements are based on an ASUS X550VX-MS71 15.6" Laptop running windows 10 and the game was opened in google chrome, 100% zoom, without scrolling down or anything like that.

4) Testing Documentation:

https://www.youtube.com/watch?v=_asgA77k_GA&t=21s

5) Commented Listings:

file:///C:/Users/adria/OneDrive/Documents/Thingy/html/index.html

Attached in Blackboard submission.

6) Quality:

I tried to use Doxygen for my commented listings but I have never done anything like this so I do not think I did it the right way. I made a youtube video for my Testing documentation and would’ve used it for a code walkthrough for the testing plan but I do not have a mic to record my voice and for it to be audible enough for a walkthrough.