This guide demonstrates one way to setup your locally computer for solving exercises on Exercism.io. When working on your solutions to exercism, why not version you code and save it to git just as you would any "real" project you plan to deploy? With Github, you can make a public repo for free that can contain all of your solutions, plus you'll be associating this nice code with your Github profile and be getting those green squares on Github! Excercism projects make excellent code to have on your Github account because every exercise itself is it's own little self-contained, fully unit tested and peer-reviewed bit of clean code that does something correctly! You can take a look at my Exercism-Solutions repo to see how awesome it is to have all of your Exercism solutions there in a Github repo. ?
Pro Tip: Use Async / Await With Act To Avoid Act Warnings in Jest / Enzyme Tests And Have Components Update Properly!
I was having a hard time recently writing jest + enzyme unit tests for a react.js project, and one of my colleagues saved the day with the await / async addition. In this post I'll go through what I was doing, what I tried that didn't work, and what we ultimately went with that fixed everything!
Recently I've been getting back into doing some algorithms coding challenge problems, and I really wanted to setup for myself a nice, comfortable coding environment that I could be proud of and that really followed the TDD principles of Uncle Ben, Ken Beck, and all the other gurus. Anyway, this is a guide for setting up simple, barebones TypeScript node.js projects for TDD. I'll show you how to set up a brand new node project, how to make your project a "typescript project", how to add mocha and chai in watch mode, and finally how to see your test results in a nice code coverage report. It's a lot I know, so let's dive into it!
I seriously love using protractor-cucumber-framework, but it can be quite annoying trying to configure it perfectly, especially when you're doing it for the first time. I was having some trouble setting it up with my recent project, and decided to write a post about this specific error that I seem to run into often (hopefully that'll change soon! hehe) when adding this to my projects.
So I'm almost finished reading this book, BDD in Action, by John Ferguson Smart, and I think it is really a fantastic book. Despite the wacky, ugly-looking cover, this is a super-awesome software development book that pretty much revolutionized the way I think about unit testing- and I think a LOT about unit testing so this must be a pretty big deal. I would highly recommend this book to anyone trying to wrap their head around behavior driven development, but in this post I'm going to reveal the crux of BDD- spoiler alert!
The posts on this site are written and maintained by Jim Lynch. About Jim...