Performo test cases dummies

6 Responses

  1. I like the style and tone of your writing/stories – keep it up! I think we’ve seen that Test Cases absolutely have to be written in a way that pretty much anyone can pull the case up and know what to do without explicitly having worked on that software or system. The trick, as the story illustrates, is explaining that and working with clients to ensure that they understand the importance. Subbed and liked!

    • Señor Performo says:

      Amigo thank you so very much for your kind words! They mean mucho to me as I am just starting this!
      You are my first comment!
      Thank you so much for the shares as well.
      I will keep posting stories with meaning and fun examples, I hope they keep being likable for you. I promise to do my best to keep them fun.
      Requests on topics are very welcome!
      Again thank you so much! Me gusta!

  2. silver1tung says:

    I truly enjoy the writing style. It makes clear the struggle we face with the 80/20 rule of thumb, where we as performance testers need to only focus on stressing the load with the 20 % of the business processes that really get the most attention and really only hit the server. Way to go , but then again it really depends.

    • Señor Performo says:

      Gracias amigo!
      I appreciate your support so much, and that doesn’t depend!
      Thank you so much!

  1. July 18, 2017

    […] Wrong! Often, while you are following them, they will specify some steps and you will be like WTF. “What is the button that I must press? I don’t see any button”. There you can report the test case as outdated. Ask the test lead or someone in charge of it to update it . Most probably, you don’t know how to use the system. And even if you did know, the test case should be clear and up to date. I mentioned this before. […]

  2. November 28, 2017

    […] together with their names. They must follow a specific naming convention and be available on the test […]

Leave el Reply

%d bloggers like this: