addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscrossdots-three-verticaleditemptyheartexporteye-with-lineeyefacebookfolderfullheartglobegmailgooglegroupshelp-with-circleimageimagesinstagramlinklocation-pinm-swarmSearchmailmessagesminusmoremuplabelShape 3 + Rectangle 1ShapeoutlookpersonJoin Group on CardStartprice-ribbonShapeShapeShapeShapeImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruserwarningyahoo

Test Driven Ruby Warrior

So far, we've spent some time implementing Ruby Warrior and then spent a bit of time talking about how to wrap those ad hoc implementations with tests to begin refactoring.

This time we'll continue our exploration by starting from scratch and driving the design with tests. We'll see what advantages we find over the ad hoc version and see how malleable the test driven version is as the requirements continually change. Along the way we'll learn about mocking and stubbing in isolated unit tests.

Join or login to comment.

4 went

Our Sponsors

  • Corvisa

    Meeting space, food, and drinks.

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy