DPS909 - Mamadou Diallo

This weeks goal was to test our code that was written.  To begin I had my usual issue with git rebase... Lines of code that I thought shouldn't appear was appearing. From the very start of this lab I took the liberty of removing duplicate code and commiting to my master in hopes that it doesn't appear anymore for future labs. Once my code was clean and up to date, I began to create test cases using jUnit. Due to not having tested in JUnit in a very long time I had to refresh get some refreshers. JUnit testing made me realize that maybe there was more functions that I could've refactored as I only had 2 functions not including my main to test.  In regards to adding a coverage tool, luckily I didn't have to use any external tool. Intellij has a built in coverage tool that is able to generate its own coverage report. To run it one must simply run the code with coverage.  In regards to my Continuous Integration, I decided to go with maven. This was my first time using any s

For this release the goal was to have two pull request. I had to make an internal contribution to telescope and an external contribution which I made to a Data Structure repo that I've found during hacktoberfest. For telescope I decided to go and fix issue #1278 (Add docs on how to debug the backend) . I chose this issue because I myself was not comfortable with VS code and had no knowledge on how to use it. I thought that creating a doc file would be somewhat easy but what I didn't realize was that keeping the same "Syntax" as other documents would be challenging.  My PR can be found here :  Fix for issue #1278 : Created debugging file For my external pull request I actually wanted to find something new, I was looking to code something in java but found that there was lots of spam after going through multiple pages of open issues. After unsuccessfully finding any decent repo that I could contribute too, I decided to go back to release 0.2, I initially wanted to work

  For this lab the goal was to analyze my code using external tools.  Although there wasn't much coding involved, this was good a good learning experience as I did not know that such tools to format and scan for bugs existed. Using google java format I was able to format my code, other than improper spaces my code didn't need much modifications. As for the linter I used SpotBugs, which surprisingly didn't return any errors. Through out this lab my only issue was with Intellij, my plugins weren't installing properly and my only fix to that was to upgrade from Intellij community to the ultimate edition Additionally I had issues with git when trying to squash my commits. For some reason I initially my git rebase command was telling me I was already up to date, then tried to rebase my current branch to master which didn't give me any squash option as seen in the screenshot below.  After doing that I had pushed my commits and could see duplicate commits for the same code

This lab up to date had to be the most challenging lab for me. I previously had issues switching between my Macbook and Windows. This lab made my realize my biggest mistake while trying to code on two different platforms. Do not code and store things on the cloud (OneDrive) as things will clash and make your life extremely difficult.  Initially I had tried to get telescope working on windows, installing elasticsearch was very troublesome so I had switched to my mac. I made the switch over to my MacBook which made installing redis and elastic very simple with brew, unfortunately my comfort level using my mac isn't the greatest so I reverted to my windows computer.  It took me a while but since I had configured elasticsearch on my macbook when I returned to windows I was having tons of issues in the sense that elasticsearch couldn't find certain files.  I proceeded to delete elasticserach from my windows and have a fresh instance of elasticsearch reinstalled. Once reinstalled I w