It occurred to me as I was trying to clean up my code structure that it would behove me to not just clean up the code but to restructure the project to support running tests.

Front and Back

There are parts of this project that will not have anything to do with the hardware it's running on. I'm calling that part the application and the front-end of the project.

Anything involving the hardware the project is running is going to be denoted as firmware and the back-end of the project.

Learning to Test

I have not had the opportunity to work on any projects professional that have a formal testing process set-up. A staggering amount of web projects have not testing what so ever.

I learn best by doing. Show me working examples that I can run myself and tease apart and play with. Peach Pit Press has a set of books branded “Visual QuickStart Guides” and I adore those. They are perfect for how I learn best.

I understand at a high level why you want to test but I’ve no idea how to start it myself on my own project.

Always be noobin’!

A mutual on fedi, @federicomena@mstdn.mx, looked through what code I’ve published so far and gave me some great ideas on how to start adding in testing.

“You can start by deciding what would benefit the most from adding tests – code that breaks often during changes, or code that you want to refactor but not break, that sort of thing.” – Frederico

Where I am

I do not have too much to show for February because I am in the process of setting the up firmware code as a separate sections from the application code. I can run the firmware test from onboard the device(s) and test the application behavior and logic from my desktop because it will not depend on hardware specifics.

Where I’m Going

When it’s done have it set up to run in a test framework, then I will post the code and tests up on the repo. Hopefully the March update will be longer and have more to show. I’m moving in a couple of weeks so let’s see how much of next month gets eaten by that. Bye!