Testing, Pull Requests, and Ruby
In my recent meeting with Dr. Bowring, we discussed the tasks assigned to me, which involve diving into software testing and contributing to the Cirdles Tripoli Project.
The Process:
My journey began by forking the Tripoli project and setting up the upstream and origin on my computer, allowing me to start contributing to the codebase. This experience was particularly thrilling as it marked my first attempt at making a pull request, a milestone in my development journey.
I embarked on the task of creating JUnit test cases, a fundamental aspect of ensuring the reliability and robustness of software. I successfully tested three classes, one of which involved the Tripoli Serialization method—a subject I had the pleasure of exploring over the summer.
During our discussion, Dr. Bowring introduced me to Codacy Static Code Analysis—a linting software that aids in identifying issues within pull requests. Additionally, I was introduced to Travis CI, an automation and DevOps tool that streamlines code testing and builds.
Looking Ahead:
As I look to the week ahead, Dr. Bowring has assigned me the task of creating more test cases. Notably, I’ll be utilizing MATLAB to validate the mathematical calculations within a complex class that involves covariance matrices. My aim is to continue enhancing the program’s reliability and functionality through comprehensive testing.
Personal Goals:
Outside of my assigned tasks, I’ve been pursuing personal goals. I recently completed my first Ruby project, which encompasses CRUD operations. This endeavor allowed me to expand my programming knowledge by delving into Ruby, devising CRUD functionalities, configuring the database with SQLite, and enhancing the project with Bootstrap and Gemfiles.
With exciting developments both in my contributions to open-source projects and my personal programming journey, I’m eager to embrace the challenges and opportunities that lie ahead. Thank you for reading!