Archive for category testing

Inspiring Others

My “Testing in Agile: From an Afterthought to an Integral Part” is becoming a hit: I’ve been receiving great feedback and compliments from attendees and many requests to deliver it as a Lunch and Learn at their companies (drop me a note if you’re in the Houston or surrounding area, and I’ll come to your company, too!). I’m so pleased with the response I’ve been getting that I really feel like working on polishing the presentation further (better title, better description, etc.).

One of the points I bring up on this presentation is my “No GWT, no code!” movement. 🙂
As it turns out, people are responding well to that! At some conferences and user groups, when I mention the movement (which initially just came out as a funny remark), I hear attendees saying out loud “YES!!!”. But now, the coolest thing happened… check this out:

I just got to the Improving Houston office and had an envelope that came in the mail for me. What is it?

Yes, “No GWT, no code.” stickers!!

An attendee to my talk at one of the conferences felt inspired, got these made, and mailed it to me. How awesome is that?!

The realization that you’re inspiring others with your work and attitude brings so much joy, while it also keeps the flame burning, providing energy to keep pushing forward. You should try it, too!

Leave a comment

Speaking at the AgileShift Conference in April

I’m going to be speaking at the AgileShift Conference in April!

I’ll be delivering my current favorite talk, for which I’ve been receiving great feedback from people who have seen it (ranging from software developers, QA, business analysts, product owners, etc.):

Testing in Agile: From Afterthought to an Integral Part

Testing cannot be an afterthought; it has to be an integral part of software development. Is it something that QA teams do? Or is it part of a developer’s duties? Do business analysts play any role in it? What is test automation? Unit test, Integration test, Test-Driven Development, Behavior-Driven Development… what do those mean?! This session addresses all of those questions, as we talk through the importance of tests, the collaboration among team members, the techniques, and practices around different kinds of automated testing.

I hope to see you at the conference! 🙂

Leave a comment

Learning New Languages and/or Libraries

When I started to work on some Ruby on Rails projects almost 8 years ago, I knew zero about it. Instead of jumping head-first into learning the language (Ruby) and the framework (Rails), I started by learning how to write unit tests for it. That was the tiniest thing I could do to get my feet wet (passing tests give me that instant gratification we all crave for).

Learning how to write unit tests in whatever language should be relatively easy; if it’s not, I probably would not consider working in such language to begin with!

After learning the basics of writing tests, I can implement simple things in the language however I can, which back then, it meant I was “speaking Ruby with a C# accent”. That’s ok, because once I see my tests passing, I can poke someone who knows a lot more about the language than I do to teach me the better ways to both write the implementation, as well as the test.

I’ve documented my experiences back then on a two-part article (part 1 and part 2). While those posts are already over 7 years old, most of the ideas and approach I covered there still apply today.

More recently, as I started getting my feet wet on ReactJS, one of my first questions was: “how do I write tests for this thing?”.

I like to first learn how to write my tests using Given-When-Then. So, I’ve learned that if I use Jest to test React code (or even plain old Javascript, for that matter), this is how I can get started:

That gets the ball rolling for me…

Leave a comment