"Test case" in a "Testing Court"

This time let me start with a situation when a test case is made to stand in testing court for hearing. With this I like to say the importance of test case and its objective Lets start.

Attorney(Tester): what is your name?

Ans: My name is “Testcase “

Attorney: Who is your creator?

Ans: A good tester!                              

Attorney: Where do you stay?

Ans: With all the necessary steps to reach me, I stay in different places like Excel sheets, test management tools

Attorney: What is your role of assuring quality of any application?

Ans: It all depends on my creator i.e Quality process is initated by him I just follow it

Attorney: we say your spoken words tend to decide quality

Ans: Yes of course if the steps used to reach me behave in the expected manner I will be allowed with Green pass to next level else a Red token with appropriate incidents will be raised reaching developers

Attorney: What is the necessary feature to see an ideal test case?

Court was adjourned as time elapsed :) explained below

 

So it’s better to know importance of each and everything with time because time values more than money so as tester what is that I need to know about designing test case.  

To say more detail about the above question as test case creator we should know the ideal features/objective of good test case. So what is it?

What is the objective of test case?

                   Atomic                  Find defects                        Maximize bug count

Assess quality                          Verify correctness of the product

                     Assure quality                                             be More informative

So Testcase starts with its identity and leads with the collection of steps to completion resulting in the expected /actual results and falling in a test suite community.

Designing good test cases is a complex art.  So what helps in designing it?

• Good knowledge of the domain
• Understand the risk involved
• Knowing the steps in completing the task with expected results and necessary pre requisites
• Setting up the priorities and severity
• Keep it more informative and descriptive.

Advantage:

1. Gives an approach, Description, Pre-conditions to achieve the expect result.

2. Test Cases are useful while writing Traceability Matrix.

3. It shows or avail the traceability of the entire requirements.  

Disadvantages:

1. Miswritten Test Cases or human errors in the test cases can only cause the project failure.

"You are the creator of test case be proud of it “

Am I Good Tester?

When I started my career in Software testing I thought whether the domain that I chosen is of good one or not , later on exploring myself felt that there  is something that I can achieve in this . A simple vision of creating the sense within the Software testing  led me to explore many things .

On getting my self into the Testing the only question that started to poke me is “Who is a Good tester “

On making successful survey and having discussion with the persons who have achieved something in this field. I got some checks to test whether I am a good tester

The Checks for a good tester:

• Should be passionate about testing
• One who have good eye over the defects
• Good communication so that he can express the defects in more convincing way to all
• One who finds quality bugs
• Analytical and Logical  Thinking.
• Error Guessing Skills.
• Problem Solving Skills.
• Creative,
• Enthusiastic
• Diplomatic.
• He should not be biased by developer.
• Should have an attitude to break the system and test if it's required
•  He should never assume the things.

OMG checking out the above list I felt what is the simple way that I can achieve all those.

Then I found if I follow simple principle “5 W’s and 1 H “ is it achievable

5W’s and 1 H is :

                                   Who?

                                              Why?

                        What?
                                              When?
                       Where?
                               

                                    How?

The way  of applying this  :

 When any application is given to test be clear in vision why to test and  understand What to test respectively  How  to test  , when and where to present findings so that it is convincing and clear to all  .

Finally,be accountable if any one ask “Who” found this quality bug

Is it simple ?

The day I started to follow this  above principle helps to acquire the qualities of a good tester .

So why you all should wait try  this simple principle and be a Good tester 

Stick this note at your working Desk