Seeing And Knowing Magic

Working (well-thought) software feels like magic when we use them, even when they do not magically build themselves out of nowhere.

To be a software tester means to see first-hand how software development actually happens, in real-time. They discover how programmers code what they can from concepts and (almost always) incomplete ideas, they catch themselves and their co-testers trying to cover all possible valuable test cases, they find user experience designers hampered down by client whims, and they learn how hard it is for product owners to figure out customer needs. Requests become examples that turn into a collection of links, copies, and buttons, which then grow into prototypes, then features, eventually complex products. The apps that we love in both mobile and desktop or in cars and toys gets built by people who enjoy creating digital stuff that help people do their work or have fun. Here, the software tester finds herself in the middle of an exciting adventure – on journeys to finding solutions to worthwhile problems. There are travels along the way – some smooth, some rough and bordering burnout, some really easy, others enormously difficult and sometimes doesn’t make much sense – and there are lots of stories that can be told. And always, the team tries to go forward on a sustainable pace even when there may be unforgiving deadlines, crappy customers, incorrect examples, heavy rains, failing servers, health problems, even personal irrational worries that’s just around the corner. There are ups and downs, and the software tester sees and knows that everyone in the team that’s actually building the feature from imagined descriptions is doing what’s possible in the moment, everything in their power to solve one problem at a time, day in day out, given the situation. There are successes and failures, and then working software goes live and becomes magic.

All because the people who made it together shared their magic.

Advertisements

5 thoughts on “Seeing And Knowing Magic

  1. Hello Jason,
    Would you be interested in making a Selenium Webdriver tutorial on your blog (or a separate)? With Java. I have seen your github repo and I like the way you code, and would like to learn how to do it myself. It would be greatly appreciated.

    Maybe a tutorial on your bookingEngine class, because that one was the most advanced one? Or maybe a fresh one on another application, where you apply the same logic and structure, because that is what I like about your automation.

    Thank you.

    Reply
    • Hi Adam,

      I appreciate the comments, thank you. 🙂 I am actually thinking of creating a course on Webdriver in the near future, about the things I learned for the past two years. It’s still in the planning stage though. Anyway, I can’t promise anything for now but I’ll try to write something that could maybe explain how I do things. If you have a specific site and test in mind that you would like me to write a sample code of, let me know. 🙂

      Reply
      • A tutorial on automating the application that you are working on, with the bookingEngine, would be appreciated. 🙂

        A question: why do you “overparametize” your methods, instead of just making a new method for that condition? I know that it is good to make your code generic, and DRY, but a lot of if else statements might get confusing. 😛

        But maybe a blog post about your architecture/algorithms would be enough? Why, and how you automated the way you did?

      • Good questions, and you’re probably right that I should refactor those methods that have too many parameters. I’m actually still in the process of learning the ropes of good coding practices as well as good test design. To answer that question, I can only say that it happened only because that was my preferred coding style right now. I will keep your suggestion in mind, thanks. 🙂

        I’ll try that blog post idea, though don’t expect it to be up too soon. As for how I learned Webdriver, basically I enrolled in several Udemy classes, wrote code almost everyday (it helps if you have a specific site/app that you really want to test), and googled answers to questions (I found Stackoverflow and good blogs that way).

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s