Quote#1

Quote1 (Design2)

I have decided to start a testing quote series named “Hear Me Quote” on this blog. I will be sharing interesting quotes (may be jokes, metaphors etc. too) about software testing and quality assurance under the said category. There would be a new quote every Friday so there is that to look forward to 😀

Share your favorite quotes with me in comments and I might add them in the next post(s).

4 thoughts on “Quote#1

  1. Putting the effort into designing tests is crucial. I recently tested an area that had already been signed off by a relatively new tester and superficially, obeyed the story perfectly but my tests looked at how the user would work with the functionality as well as checking that the code obeyed the acceptance criteria on the story. The code obeyed the story just fine, but when I thought about how the users of the system already work and what they would require from the new functionality I found a flaw. The story was to allow a user to raise an action against a fellow member employee, the system records employees some of whom may also be users of the system but many may not. I found that I could raise an action against someone who couldn’t access the system and, therefore, would have no idea there was an action against them.

    When reporting the fault to a dev I had the following conversation:
    Me: “But you’re sending an action to someone who doesn’t have access to the system”
    Dev: “That’s right, the story said the user needed to be able to raise an action against any employee. It didn’t say they had to have access to the system – it’s the sys admin’s fault for having employees in the system who aren’t users”
    Me: “Why would you assume all employees have access to the system? Why would the cleaner or the caretaker need to be able to log on to the MIS?”
    Dev: “That’s not the point – the story didn’t say that all employees wouldn’t be users and would need an alternative method of notification”
    Me: “And it didn’t occur to you to ask what will happen when you’re logging a critical action to someone who won’t see it?”
    Dev: “Why would I? The analyst wrote the story so they know best, so the sys admin needs to make all employees users of the MIS, even the cleaner. It’s obviously a bug in the legacy system that all staff aren’t users.”
    Me: “Really? Our cleaner doesn’t have any access to the MIS so why would we ask that of our customers? Can’t we at least flag that the user needs to consider alternative notification?”
    Dev: “My code does what the story says.”
    (The analyst is new and doesn’t know much about how users use the legacy system, the dev hasn’t any experience of the legacy system.)

    The moral of the story – include your experienced testers in your story reviews, not just the new tester who will be working on it and doesn’t yet know the system. New testers need to understand more than just the area of a system they’re working on – market knowledge, user understanding and a good idea about how their section of the system sits within the whole is essential.

    Like

    1. I completely agree with you. There is an app that my company has been developing for about a year. In a year, as more and more functionalities are added and more features to existing functionalities have been added, the app has gotten complex beyond belief. My experience of testing an app for this long a time, I have come to learn that had I been new to it, I wouldn’t be testing it as well as I do. I believe that not only should you know how testing works but primarily you need to know the system that you’re testing in detail. Only then would you be able to hit it where it hurts.
      Although, considering the quote, I think it applies for when you do know the system. How else would you design better tests if you don’t know your system well?

      P.S. Thank you for your comment, I think I should write a post about this. 😀

      Like

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