காத்துக்கிடக்கிறேன் உன்னைக் காண....

காலையில் கண் விழித்ததும்
வந்துவிடுகிறது உன் நினைவு..
கனவில் கூட வருகிறாய் நீ
சில நாட்களில்


வேகமாய் குளித்து
ரயில் நிலையத்தில் காத்துக்கிடந்து
படியில் தொங்கியும் அலுவலகம் செல்கிறேன்
உன்னைக் காணும் ஆசையில்


காலையிலேயே உன்னைத் தேடிய
என் கண்களில் ஏமாற்றமே
கவலையுடனே தொடர்கிறேன்
என் வேலையை


அருகில் பணிசெய்யும் சிலர்
சினிமாவும் அரசியலும் சில கேலிகளும் பேச
என் நினைவில் நிற்பதோ
நீ மட்டுமே


இடைவேளையில் தேநீர் குடிக்கையில்
பார்த்தியா டா மச்சி என்று கேட்கும் நண்பனுக்கு
சோகமாக உதிர்க்கிறேன்
விரக்தியான பார்வையை


சோகமாக திரும்பிய எனக்கு
கொஞ்ச நேரத்திலேயே இன்ப அதிர்ச்சி
கிடைத்தது உன்னைக் காணும் வாய்ப்பு
அதுவும் மூன்று முறை


இன்றைய நாளுக்கான நிம்மதியோடு
சென்று அமர்ந்தேன் மதிய உணவு அருந்த
எதிரிலே இருந்த நண்பன் கேட்டான்
மச்சி...மூணு பக்(Bug) கண்டுபிடிச்சிட்டியாமே....


(உங்களில் ஒருவன்...Software Testers)

Testers and Software Requirement Specification (SRS)

The most important work of the testers is converting the SRS to the test cases. I shall point out some important notes which need to be considered before starting the Testing.

1) Don't start your testing before understanding the Specification completely

2) Read the Specification document atleast two or three times

3) Read each line of the document carefully and understand.

4) Don't hesitate to discuss the doubts you have with the specification

5) Each line of the SRS shall be your test case.

6) Find out the areas not covered in the SRS ( Mostly those can be the failure cases)

7) Prepare a rough test plan after understanding the SRS

8) Frame your test cases to cover SRS

Start your testing now....

Does testing process include analysing & reducing the bugs?

A tester finds a bug. What is the next step? Does he need to analyse and reduce the bug case? or he can just report it and continue testing? The perception of the people differs in this case.

Some people argue that a tester's job is not finished with finding a bug. He needs to analyse the cause for the bug and he should reduce the bug and then he has to report with clear details. 

But some other argue that tester's job is only to find the bugs. Which one is best?

I shall add some points in the tester's point.I hope the testers wont accept to analyse the bug. I also feel the same. It may be difficult to accept by the developers and the management. I feel that, after finding a bug, a tester shall report the bug with the data which he/ she has. He can add a video explaining the bug.That is more than enough. Shortly he can go ahead with his testing, that is finding the bugs.

The thing is, a Tester should always feel that there is still more bugs are hidden and he needs to find then. Tester cannot spend his time to analyse a single bug, that can be done at any time. Even that can be done by a developer. 

          And we should accept a general truth. A tester needs to test "n" number of test cases to find a bug, he may face a bug at his 2nd test case or he may get it after testing 100 cases. And many factors decide this gap. Tester's concentration, knowledge, experience, logical thinking, quality of the code, the difficulty of the application etc..So probably he need to spend more and more time with the application to assure the quality.

So definitely the time which is spent to analyse the bugs, will reduce the Tester's concentration and continuity of testing. This will have direct impact on the quality of the software. So we can say that for a tester, "Finding more number of bugs" is highly important than "Analysing the bugs"

Why this blog?

First I thank all the readers who read my blog. Why do I write this blog? This is just to share my software testing life with others. I am not much experienced to advice the testers, but I hope I can direct the entry level testers in the correct path. And my hearty thanks to Mr.Gopal, Senior Test Engineer, Amadasoft India (P) Ltd., Chennai who taught me the testing from the scrap and trained me. I will feel good if any one of my post in this blog is useful to any tester. I dont have enough english knowledge to write a blog. Kindly bear with my English..

Wilson.R

Author.