Lab 8



    This week our task was to add tests to our Command Line Interface repository we have been working on this semester. The first thing I did was to read my README.md. This was the first thing I did because it has been a while since I have worked on this repository. Reading this document helps me remember where I left off and remind me off. In addition, I try my best to make small updates to the README file every time I read it. This helps keep the documentation up to date while refreshening my memory on how to use my program. 

    The framework that I chose to set up for my testing was Unittest. I chose unit test because, while I was researching, I read that developers use unit test since it is easy to read, write, and reliable. The tutorials and steps given on the document were very straightforward and allowed me to start writing my test with little effort. Although, this was my first time writing tests, by reading the documentation I was able to create two tests that checked the response codes from Google.


    For me, the hardest part about this lab was adding continuous integration onto my Github repository. I had a difficult time configuring the YAML file. The problem was that I had created the fixes on the Master branch to resolve the issues on the new branch with the Continuous Integration workflow. This resulted in me creating multiple workflows in order to get it to work, however, It was all worth it at the end. I had a beautiful workflow program running. This brought us back full circle to the documentation, since I had updated the documentation before I had started, It didn't take much effort on updating the README.md. I simply demonstrated how to run the tests.


    Creating test on someone else’s repository was surprisingly simple. This was due to the fact that the repository owner and myself both used Jest. This made the testing very simple to understand since I have already built test using Jest. It was interesting to see someone else’s code and how I could try and break it. A good example of this would be how I tested for an empty object or an empty array. I’m not exactly sure how you would send in an object on the rate as an argument however I thought it would be still worth checking. It seems like I will be building tests for the rest of my life. It's time to get comfortable writing tests.



Comments

Post a Comment

Popular posts from this blog

Working with others

     This week our course was given the task of creating a cli command, which included our code being reviewed by one of my classmates. Initially, this gave me some anxiety as sharing my work with others is not my strongest suit. Nonetheless, I created a post asking if anyone was looking for a partner and Michael Appeared.      It turns out that having someone look over my work was much less scary than I had initially anticipated. Working with Michael was actually fun, and having the opportunity to look over someone else's work was a great learning experience for me.       With another pair of eyes looking at my code, Michael noticed errors and instructions that I was not addressing. Some instructions I had forgot to mention include the fact that my program requires bash. It did not occur to me that most of us live in a Windows Operating System. Another missing component was my Blog link in my READme. I had forgotten to include a link to my blog! As soon as Michael notified me he w
Read more

We are off! V0.1

Initial Release V0.1  Our first Assignment was to create a command-line tool to check and report dead links in a file. Status code 200 would be considered "Good", 400 and 404 is "Bad", and all other status codes are considered "Unknown." My first experience creating a release was nerve racking. With no instructions on how to approach this problem, I started to brain storm ideas, and eventually started questioning my abilities. Inevitability, I chose to do my assignment in bash since it would allow me to colour my code, as well as create a command line tool. Overall, the first assignment was fairly simple to use. Simply clone or fork the repository, open up bash, and run the command. Command : ./cliCommand <filename> NOTE: This project will need Bash installed on your machine. Mac OS has bash built in, however, Windows OS may need to install Bash. Please feel free to play with codes, if you have a crazy idea, then pull request :) Usage and Features Us
Read more

The Progress

This week I decided on a repository to work on, the telescope repository. I was excited since this was a front end development issue. I had never created my own component before, however, I have some prior experience using React. I started by creating a bottomBar component and locating where I should add this component. I located the PageBase.js, the mobile application interface, and added the component to the bottom of the page. I started by creating a div with a red background to make sure I was on the right track. since it has been a couple months that I have not worked with React, I started with the most basic tasks, such as, creating a react component, a  div element, and rendering the component I made.     After confirming that I did not break anything, I started designing the layout of the desired BottomBar. The idea was created by  agarcia-caicedo,   proposed a bottom app bar t o improve mobile usability. If you're curious on the original idea you can check out his 
Read more