Late last week I finally got into some completely novel concepts for me in the precourse work. The remaining Git ideas were fairly basic, but did describe the workflow HR expects us to follow). Not much interesting there. However, I then moved on to the section on Automated Testing, about which I had only had a vague understanding of the general idea before.
Yesterday I worked through the resources provided to learn about Chrome’s debugging tools. I haven’t had a chance to implement any of them yet, but they look like they will be extremely useful. I had been using the console and a few other tools provided by Chrome, but I didn’t really know what I was doing or how to use these effectively. I will definitely want to review this section again (and probably again).
Writing the first few functions was a bit slow, primarily because I was still picking up on little nit-picky syntax requirements and figuring out my overall workflow. Now I’ve got a pretty good system worked out, and the latest function I rewrote only took me a few minutes. Basically, I write what I THINK the function should be, test it in the browser using the original testing file from HR, then test it in Node to get additional feedback. Then I’ll try it out in JSFiddle to tweak it until it works there, test it again in Node, and if that passes, double check it in the browser (this really isn’t necessary, but what can I say, I’m a perfectionist). I’ve also been committing all of this to a separate Git branch, so that I don’t get all of the Node files mixed into the master branch. Once I’m done, I’ll merge all of the changes to the file that contains the functions to the master branch, leaving out the Node files.