Day 4 of StarEast – Automation Testers

7 Habits of a Highly Effective Automation Tester – Krishna Iyer (ZenTest Labs)

Day four of the conference, I went to 4 tutorials and heard some interesting key notes, however the one that stood out the most was 7 habits of Highly Effective testers. I want to share some of those habits and what I was able to take away from this presentation.

  1. “The Habit of Strategizing”
    1. This first method is really the way we plan our tests before we actually go ahead and implement them. Do we as testers spend enough time thinking “How can I make these tests more efficient?” Can we combine tests to test multiple levels without having to re-run/re-write an end to end test every time we want to test something. We need to take the time that the proper testing effort is being taken that compliments the product we are testing in the best way. Not all products require the same sort of test tools and testing methods.
  2. “The Habit of Simplifying”
    1. This is the idea that we need to do less complex and repeatable tests in order to increase ROI and immediate test feedback.
    2. Prioritizing the more complex testing on what gives the most coverage first.
      1. Automating Every Single Possible Scenario usually ends up being time wasted, when stronger more repeatable tests can be created. Also need to consider test maintenance, “Can you maintain the amount of tests you are writing, without spending to much time, updating broken tests?”
    3. Do the results of the test, clearly point out Pass/Fail?
  3. “The Habit of Seeking”
    1. How is the product designed, and how will our test properly test each level?
      1. Functional (Functional Tests – Object Testing)
      2. Business Level (GUI – Automation)
      3. Unit Level (Unit Test)
  4. “The Habit of Separating”
    1. Realize the parts of your tests, what are most susceptible to change, and try to separate them from your tests into more manageable pieces. This allows you to update the tests when pieces change such as.
      1. Data Setup
      2. Property Changes
      3. Flow Changes
    2. Building your tests in pieces allows greater re usability of the test, and also reduces maintenance.
  5. “The Habit of Storing”
    1. This is again the focus on re-usability. What is more important, that the Data is re-usable or the tests itself. Will multiple tests share multiple test data? Will this be still an accurate test scenario if so?
    2. The more your test data and test cases are re-usable the higher ROI on your testing.
  6. “The Habit of Saving”
    1. When to test? Ask yourselves these questions before you begin a testing effort,
      1. Is the product complete enough to begin testing/test planning?
      2. Do you have enough time to implement testing and gain feedback and changes by the development?
      3. Is the product stable?
      4. Can you estimate and plan in advance?
      5. Do you have requirements?
  7. “The Habit of Selling”
    1. Can you give metrics, highlights to why your testing is valuable?
    2. Send status of your testing results to your team and management for them to understand the Quality of the situation.
    3. Are your tests shippable. Could you package your tests with production releases as away to run verification on code when it is updated on the client side?
    4. Be proactive – Don’t sell short Quality, without it your product will most likely fail.

Leave a Reply

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

You are commenting using your 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

%d bloggers like this: