Posts

Release 0.4 Final

In this release, I contributed in the  binari project, creating unit test cases for React components. These test cases are testing the components from the user's point of view, instead of internal implementation details. For example, I have tests to ensure that some action happens when a user clicks on a button. Here is the command to execute the test cases npm run test The test cases test the components as the users commonly interact with them. I create test suit for each component. This project taught me how to write effective test cases. I also learned to look from the user's perspective when testing the application, ensuring that the components are working as expected. If they do not, I know where the problem is, thanks to the test cases. I created a PR for the test cases. At the moment I am still waiting for some feedback for my PR.  Issue: https://github.com/BrandonArmand/Binari/issues/77 PR: https://github.com/BrandonArmand/Binari/pull/78
Post a Comment
Read more

Release 0.4 Progress

In this project, I have started creating test cases for react components. I have test cases for react components called rending snapshots and test cases for react components called clearfix. I am stuck on expanding the test cases to cover the whole function. I have managed how test cases work in react components. I am planning a different approach to looking at examples of test cases for react components. This way, I can see how it can be done. From there, I can figure out how I want the test cases to be done. This is done using test suites, and then I use it or test for each test case.
Post a Comment
Read more

Lab 10 Blog

In this project, I used npm to publish my site by following the npm guide. npm guide  I created onLoad.js that prints the demo message. I installed my project using the command npm install text-ssg-tool Then I updated my package.json file to version 1.0.0 for the initial version release. Then I ran the command  npm publish  to publish the site to  npm.  Then I added the changes in git. Then commited the changes on git.   Then I pushed the changes on git. Then I followed the steps in my README.md file to simulate someone else running and testing my program. I noticed a few mistakes in my  README.md file. I made the corrections  in my  README.md file. Then I reran the command  npm publish to republish the site to npm.  Then I added the changes in git. Then commited the changes on git.   Then I pushed the changes on git. Then I got a classmate to run and test my program. There was no issues. My partner had no issues at all with running and testing my program. Everything went flawlessl
Post a Comment
Read more

Release 0.4 Planning

 For this project, I will be working on the Binari  open source project. In the  Binari  open source project, I will be working on adding test cases for react components. At the moment there is no effective way to test the code. Testing by a human is not effective and is time consuming and is error prone. JavaScript files with react components will have there own unit test cases testing for different scenarios.
Post a Comment
Read more

Lab 9 Blog

In this project, I created my GitHub Actions Workflow by going under the actions tab and selecting Webpack for my workflow. Then I committed the webpack.yml file with the default value without changing anything. Then my workflow got executed, and everything was successful. I got the green checkmark for all builds. Then I created a bug. Then I added the changes in git. Then commit the changes on git. Then I pushed the changes. Then my workflow got executed, and the workflow failed on the build. Then I fixed the bug. Then I added the changes in git. Then commit the changes on git. Then I pushed the changes. Then my workflow got executed, and everything was successful.  My partner's testing setup had lint running right after any commit. Writing test cases for a project I did not create required time to understand how the code was working and why my test case was failing before making the modifications in the code to have the test case I created to be successful. PR: https://github.com
Post a Comment
Read more

Final reflection for release 0.3

 I did a code review in the telescope  project having a Russian Speaker review the Russian language.   issue: https://github.com/Seneca-CDOT/telescope/pull/3765 I did a code review in the  telescope  project checking button text on youtube and twitch form to check if text is displayed correctly.  issue: https://github.com/Seneca-CDOT/telescope/pull/3760
Post a Comment
Read more

Release 0.3 Internal Project blog

For my internal project, I worked in the open source vscode-seneca-college project. I found that README.md file was not descriptive enough. There was also no CONTRIBUTING.md file. This would be a problem for new contributers. There is nothing to tell them how to contribute to the project and how to install the required dependancies and how to test the project to see how it is working. Issue 8 I created my own fork. Then I cloned from my fork. I created a new branch using the command  git checkout -b issue-8 Then I ran the command  npm i to install the required dependancies into my project repo. Then I typed F5 to test the project. I tested to make sure I was getting the hello message as a prompt in a new vs-code window. A new window will pop up with a hello message. I am now in debugging mode. I can debug the code to find out what it is doing with the step forward step inward step out of buttons. Or I can press the red square to exit debugging mode. Then I added instructions in the R
Post a Comment
Read more