Tester's Prayer

I find this when i organize my last year notes. :) Now i smile when read this but  sure i was in great hurt while wrote this prayer. 

Web Development->Website Design and Development page:

Appropriate tab doesn’t highlighted in 'Related Services' block in right navigation bar while the same page get displayed.

What to enter in this field, i feel so sad..,

Lord please grant me the mercy from HR eyes.., :( and am expecting eagerly for the Team split action. When it will happen..? *?

Lord, Please give me the good hard working team which is always treating a men as men.., From that team i have to shine to glorify your name., Lord i give this issue in your feet as per bible say, cast your burdens upon me". Lord you are my Shepherd enable me to hear your words rather than the words of men. Father you know the problem which is happened here., and u know my heart, i bow my self at your feet.., lord plz plz forgive me for my useless words. your mercy is endure for ever.  You are my Saviour lord.., Plz help me, i never behave like this.., Please be have patient on me.., In Lord Jesus Christ name i pray.., Amen..,

Thank you so much for hear my prayers.., 

Some points to share...,

Dear Tester(Am saying this points to me),

• Don let the developers find bugs in your bug report.See, a tester hide in every human in the world. 
• Don command the developer, you are not the captain of the ship mind it. EX: The title should be in centered alignment. Above line should not be in bug summary or description, may exists in the Expected Result area as per requirement.
• Tester's success is on quality of the End product, not only finding number of bugs in application(But this one too important).
• There is no use of your bug report, if those things are not accepted and fixed by development team means. this is the greatest failure of tester.
• While testing the application, go through some of modules or functions you feel it darkened, and you need more clarifications regarding the module/function means, don hesitate to contact fellow tester/developer. You are the first client of the application, so you have to be know all things about application. 

Completed? Not completed; Not completed? Completed

Its like a Game, you can say completed yet you are not complete, like wise Not completed still you complete.
Tester playing this game every of task and every day.
Some times say completed, but not completed yet. and some times will say not completed even completed with that.

We cant say this tester saying lie, same time its not true fully. let say this partial true, partial lie :) The worst case in this is tester don know some situations whether completed or not completed. what to do say this case..? :)

This game not at all give joy or happiness but have to play with even don’t like it. Most of the testers in the world playing(shrinking) this game with pain i guess.

Oh! My God! When will this tester get out and set free from this game? :(

Don speck with out proof

Its far better to tell, yes i did test with this scenario, but now am not accurate with it rather than, I did test this scenario before and it was working fine.

All because, Anything may happen to the software at any time. You see, we cant able  to be sure whether we have the same tested code moved to live all times., You don know, you cant able to control the things happened in software beyond your hands.

One software tested by the tester and got approved by him after the 10+ number of iterations. Finally code get moved to live server, One particular scenario not work properly in live server, client experience the same issues and shoot out to tester. Tester got amazed, because that particular case already raised as bug by him and get closed in one of the iteration, but now the issue exists in live server.,

There may be number of reasons behind the scene.
Tester raised N number of bugs in first iteration send the report to development team. Development team fixed the bugs and sent  updated code to tester. Again tester tested the application, cross verify the N number of bugs get resolved or not, if the bugs resolved means change the status of the bug, if not means reopen it and sent report to development team, same time this iteration test again found N+ bugs. In third iteration, tester test with the reopen bugs and the new one raised in iteration 2. So then what will happen to the bugs closed state in Iteration 2 ?

Normally the testing time gradually decreases in every additional iterations. so is in it possible to to test all the test cases in every iteration? It is a challenging thing to deal with, :(

Why the Bug posted by tester get rejected by developer as "Not an Issue"?

Case #1 Tester understood the functionality of the application wrongly.
Case #2 Dev team misunderstood the scenario mentioned in bug report.

Tester only needs to take full responsible for both cases. In first one, lack of understanding of the project leads to raise functionality of the application itself as bug.

• Tester consider the one action exists in application as bug.
• So she/he try to reproduce it 2 more times.
• Note the steps to reproduce the issue.
• Took screen shots and mentioned the bug exists in application in that image.
• Wrote a bug report, set priority and severity.                                             (Any how, all this process took at least 15 mints i guess. :) )
• After that the bug sent to developer team.
• Developer read the bug report.
• Get confused himself/herself.
• Try to reproduce the bug using the steps.
• And search the Documents and verify whether its an issue.
• Found the same mentioned in document as functionality.
• Told this very good news to fellow developer and laugh/irritate some times.
• Forward the same message to their head.
• Head look on to the bug and verify it with the documents.
• Confirm it is an functionality and not an issue.
• And Mentioned the same status in bug report.

Oops! it is a loooooooooong process, even a single issue ate precious time of entire team.

 And in second case, tester is not like to write a bug report like poem, even if it is not understood by developer means, may following are the reason:

1. Scenario mentioned by tester not having clear steps:  Developer cant able to reproduce the bug by the mentioned steps.
2. Required info not exists in bug report:  some of the bugs only exists for certain type of input data and precondition., In this situation tester should mention test data(it may by a file, info, etc)and pre condition properly.
3. Spelling and Grammatical mistakes leads to confusions in development team end.

Testers are not Prophets but have to be while reporting a Bug.

Tester A, test the application at first time and raised number of bugs. Following bug is too the one of them.
Summary: In application XYZ, Form ABC doesn’t get submit properly.
Steps to reproduce:
Enter the web link in browser.
Enter data in ABC form in that page.
Click on 'Submit' button and verify.

Expected Result:
 Form should submitted, success message should display properly.

Actually Result:
 Blocker error page get displayed while click on 'Submit' button means.

Risk: Cant able to receive the data entered by user in that form by admin.

Tester finish the 1st iteration and sent a Test Result to development team. After a long time, tester received testing pack to do iteration 2 test.

What happen to that bug At Iteration 2:

Actual Result: Iteration 2
 Blocker error page doesnt get displayed while click on 'Submit' button but at the same ABC form doesn't get submitted. No action took place while click on Submit button.

Tester finish the 2nd iteration, sent a Test Result to development team. After a short time, tester received testing pack to do iteration 3 test.

 Actual Result: Iteration 3
Form get submitted, admin receives the data entered in the form by user. But while click on 'Submit' more than a time that much time admin receives ABC form info.

Risk: Admin receive duplicate data from front end.

Process goes on like this.....,

 Actual Result: Iteration 4
Form get submitted, admin receives the data entered in the form by user. But while click on 'Submit' form get closed immediately but still the web page get loading, while stop web page loading means, admin not receive the ABC from details.

Risk: User consider that from get submitted while click on submit button and close the application immediately. But web page took some time to submit the form, If user close the application immediately while after submit the form meas, there may be a chance to loose user ABC form info.

Actual Result: Iteration 5
Processing symbol get displayed while click on Submit button in ABC form. can able to edit the from text fields while it get processing.

Actual Result:Iteration 6
:
:

There is no end for this :)

Is this issue get fixed at less number of iteration, while tester write Expected Result as follows means?

Expected Result: Iteration 1
 Form should submitted while click on 'Submit' button.
 success message should display properly.
While click on 'Submit' button more than a time means, form should not submitted that much time.
Admin should not receives duplicate entry.
Form should not be editable while submit action processing it means.
Form should submitted properly, even if user close the application immediately.

I've write this Expected Result after a N number of iterations., Is in it possible to write the same in First iteration itself..? :)
TESTERS ARE NOT PROPHETS., If they may be some times, this case their prophesy doesnt get right at all the case. 

Testing Completed?

 Testing is not a static task, its a process.As tester we test the application in our desk while software in maintenance/development/testing mode, If it move to live, client and N-number of users use application.The test cases run by us in our desk get run again and again N number of times.So the process get continuous in some other name. 
But most of the situation, it consider as task.., :) 

 Consider the Text Field in one form, that accept numeric value 10 to 9654321987946545. Testers may write test cases for field, so many different input data and may try to automate and check with more number of test data with that field., Well, after all process, can able to assure 100% the field never accept invalid data?? 
 In Some other way, Completing test comes under some different scenarios : Time, Money,Number of Passed Test cases, Standard that client want.., etc., Answer given by most of the managers(i guess) based on this criteria itself. 

 In Software testing, we have more than 250 types. Load test, Stress test, Integration test, User acceptance test,White box test,soak test, volume test, negative/positive test, ad-hoc test, Exploratory test, static, dynamic test.., etc., etc., 
 Even if test the software with that more than 250 types, after that too, its impossible give the answer as 'Yes' for this question, "Is it complete testing?". Because as all we know Software is versatile, continuously changing thing, cant able to freeze unless if it is not in use. :)

 Why do we cant able to complete the test yet? 
Last two decade Software testing field has much growth., we have N number of tools/resources(Yes, they not enough, and not enough tested itself :) ) in our hands to do the test effectively. But yet why do we cant able to attain 100% test completion., ?