Test case writing

A tester have time to check with mails, can able to read software testing blogs, can able to participate testing forums, like wise, if he/she has time to write test cases, and can able to manage those cases, can able to update eventually when ever the new changes made with the application.Above all client is ready to pay for this work, means there is no issue to write test cases right?

But now a days, 'Testcase Writing" considered as ancient process. And why it considered not at all suitable to for current trends?

Tester's Prayer

Dear Heavenly Father,
Thank you so much for being with me,
Guide me to find all the bugs early in the project., and give me the wisdom to post the bugs as detail as possible, so that developer understand and resolved it soon.
Give me patient, to deal hard times and problems in my team, project with smooth way. Enable me to be a peace maker and to give full support to developer and team to solve the issue.

In Jesus name i pray., Amen.,

Bug in Reopen state.., still..,

1)Bug still exists in recent iteration too.
2)bug not get resolved as like the way the tester want.
3)The bug not get resolved as like way mentioned in the document.

First point is deal with developer,no action took place in the application, relevant to the bug. So the bug exists in the recent iteration too.

Other 2 points, is about variations of Expected Results of the application.
Yes, the tester's expectation and the actual functionality may get differ some times. why this mismatch happen?
The project has document specifications, those data not transfered properly to testing team.
There is no test cases document prepared and maintained for the application or there may be a test case document exists but with out expected result column.
What? Test case document with out expected result column?
yes, some times test cases document prepared as per the code works. How means, tester executes the code and understand the functionality and prepare test cases based on this.
Tester did the test with the application with their own heuristic way.
So when the bug get resolved?
simple, the actual requirement of the project should know by development and testing team to come across this kind of mismatches. 

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. 

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., ?

What the priority and severity of the bug means about?

• In form * symbol is missing for mandatory fields.
• The fields accept invalid data. 
• Validation message doesn't get displayed properly. 

Yes.,Above listed things are the validation issues, those issues doesn't get much severity or priority in developer's concern some times. Above are not a bugs in application? But why it doesn't get much attention.
Consider the Registration form in one ABC application., If that form nor properly validated means, then could not able to receive the real and correct input form the users.
'Email" field exists in the same form, and once user register with the application, conformation mail sent to appropriate user's mail. This is the functionality, and perhaps the developer had no care about validation while code this registration form and forgot to code mandatory option for 'Email' field.
The same bug raised by tester but its priority was low all because, it comes under validation category, application was released.
And user came and view the application, wish to register with the same.User enter her details in registration form, and you know this user was very clever and decided like why do i give my info which are all not mandatory..? so let me fill this form with the mandatory fields, so the user not enter her email and submit the form. As usual the user got an beautifully designed Thank You note page and the message like you will get the conformation mail shortly.., :) Alas! User is clever but yet not able to sign up with the application. Not even this one  those who all other cleverers submit the form with out their Email address not able to sign up with the application.
Morel of this story: We can prioritize the bug belong to validation category as low, but the cause and effect of same bug exists in application is huge. If the tester consider the risk of this bug means the same should tagged with the Very High severity. Am i right? :)

A tester

A tester is to test the application.
A tester is to work with developer to fix problems occur in the application.
A tester is to encourage the developer to fix the the issues in application.
A tester is to explain the clear scenario to the developer, what is actually happen in to the application.
A tester is to understand the risk, constrains exists in the project.
A tester is to have answer for all the questions raised related to the project.
A tester is to have clear vision and mission about the project.
A tester should cross verify her mission about the project with the developer, thats important.
A tester is to have patience to explain the issues posted by her, even if the same clarification asked by the developer hundredth time.
A tester is to test the application, post the bugs.
A tester is to review the bugs posted by her again to confirm the report.
A tester is to care about quality of the application.
A tester is to share the critical things exists in application immediately to the team to make it clear soon.
A tester is to have a habit of learning new things.
A tester is friendly to communicate with the team members.
A tester is to do not blame others.
A tester is to attack the application, bugs not developer.
A tester is to concern Test Coverage.
A tester is always ready to test.

A software tester should run behind on Time or Test coverage..?

If bug count increases means mutually the time line get increase.
We can not predict what is actually happening in the software before start the test ( may you have get bunch of documents to understand the functionality of the software, but after read those things you can assume the work flow of the software but not able to assure the things which you had read it in documents absolutely in the application.,
So it is impossible to set time line to accomplish test coverage of the application right..? But in practical, every software tester(i hope) test the application with the time line.,
Is in it possible to meet test coverage in estimated time line..? If a tester works based on time means, what will happen to the quality of the application, because now tester concern about the time line not about the quality.., (to be continue :) )

Earlier days of Tester

As a tester i have face following problems in my earlier days not now.., :)
1) Communication:
English is not my mother language, and in my school days too i didn't like English teachers and the subject itself, this thing greatly affect while i start to write test cases..,

2)Seeking templates rather than to seek knowledge regarding the same:
Content is more important than the document template format, it took some days to me to understand this truth.
Ex: The Test Report document should be in definitive format and at the same time the bugs which i have mentioned in the document not understand to any one means, the document is totally waste.,

3) Fairly believe the documents:
I didn't get much aware about the version control and configuration management that days. I believe all the functional and test cases documents are specking truth, i didn't knew that some of it spoke old truth., Because,of this couple of bugs raised by me went to 'REJECTED' state.

4) Lack of confidence:
When ever the bug raised by me went to "REJECTED" state, my heart start to cry. That time i don know when ever the development team reject the bug means, have to analysis the bug and understand why it get rejected., So i loose my confidence that time i thought like am not worthy to be in testing field. :(

Why you are not raise this bug in first iteration?

This is hard thing to face such a question by the growing testers.,
The following are the chances to miss the bug:,
1) Functionality of the application incomplete, not stable.,
2) Limited time line, ,
Example:
Dear tester, Start the testing process of this application and update the report before 11.15 am with out fail., ,
Mail sent time: yesterday, 12.00pm, tester come to the office and log on to the system at 9.00am. ,
3)Eager to meet test coverage given time line, with out asking or replying to the mail., ,
4)Only concern with the major functionalities of the system., ,
5)Partially believe on the development team all because of some constrains.,,
Example: Scene 1,
Development Team: Dear tester, this module X is the core pack and we integrate this in to the application., so you no need to concentrate much about this while test with the application., ,
Tester: (in mind: oh, My goodness, then i have to concentrate much in this module, but i don know enough time i get to do test with other things., what to do!!???!!) Okay developer, That module X core pack rite., let me concentrate on other modules in application., why do we spend the billable time with in it..? :) ,
Developer: :) Oh., Sure My dear tester., i know you are doing well at here :) : ) :) ,
Scene 2: later in the iterations, Tester get time to check with the Module X, and her bad time found some bug with in it., This is really bad thing., :( ,
Tester: (In Mind) Not me only do the test with the application.,!! Why this bug not get visible to my fellow testers..???!!!!??? :( (Tester started to cry in Heart Oh! My God., Why i missed this bug..? what will happen when my senior( Senior, even Senior of this tester too not find this bug in application..? This, innocent tester, don know to ask questions like this., so only she cries to the lord, asking forgiveness for her sin.., ) or the client find this bug means., ? ,
Then Tester start to pray:,
Dear Heavenly Father, ,
Have mercy on me., This is the Precious job, given by you from Heaven., I have to be sincere with my work., But am not., i miss one bug and not raise it in Iteration 1 itself., Kindly forgive me., I am having fear and i know fear is a form of death., But am your child., Lord you bring me out from sin, death, dark in to the Life, and Light by your priceless blood., Lord, Kindly guide me, and speck with me what i need to do with this thing., I place all my sorrows, fears, worries upon you Lord., ,
In Jesus Name i pray., Amen., ,
After that tester, had good sleep.,
Day-2 ,
(But in the morning, her mind continuously think about the issue, She try to over come it, she couldn't..,) ,
In morning this line comes in to her heart: Mercy of the Lord Mighty brights me like a shine of sun. She felt good and started to said again and again. After that she did her works went to office., ,
That application came to her desk at 10.30am. She started to test., she feel good and do the test well., and she have no fear while raise that new bug., ,
testing completed., ,
Internal QA bug review meeting with team higher authorities., As usual, higher authority ask this question: ,
Why you are not raise this bug in first iteration?,
....................................................................... Tester have no words to say., ,

Test Coverage all the more important

I start my testing career with the designation "Test Designer". My responsibility is to prepare test cases document for the one on going project.,
I had some sample test cases documents for the same project which prepared in earlier stage. But that time the project was in live. I don understand why test case documents were needed for this project that almost got finished.?
I started to go through the existing documents and prepared my own for every module in in the project, there was no clear documentation about the functional flow the project.
So i did Exploratory Testing ( That time i don know what Exploratory Testing means) and learn the project and prepare test case documents.,
In middle of the task only, i understood main objective of preparing this test case documents is to meet and ensure the Test Coverage of the project. On that time only i realize i was in the very important task and this documents go to sounds a lot in every project version releases.,
Before understand above things, that task was so easy to me, but after this, i felt like i was stand on the knife, If i missed out any test cases means, that may cause failure in production phase.
Oh, My goodness, i share my test case documents to development team and my senior testers and got valuable feed back from them, continually update the document.
This process get continues, every version release of the project, i updated the test cases documents of every module in the project. i didn't think test coverage is impossible that time, But it was one of my dream while i worked on the project, because as a tester we cant able to test everything in testing environment. It takes time to me to expand my mind to think out of the box.
The following alarm sound ring me in my heart when ever finish the test " I finish the test, but not complete test". I just want to stop this alarm, because some times, this sound broken my Peace, but at the same time, it give me aware about to learn new things to grow to attain my dream. I hope one day this alarm will stop :)

Testers i have met past days.,

Am not having much experience in Software testing field, but in the couple of years, i come across numerable & memorable testers in my life.
Those guys make some important foot prints in my way., I learned some good things which i have to follow., and some ones make me aware about certain things which i should not to do.,I categorize them in following titles.
Teaser:
While he got the bug, he started to laugh and celebrate otherwise, he got frustrate and started to fight with development team.Their full time work may be to glorify the application or to speck ill about the application.
Taster:
They are test and find bugs and taste it., The bugs exists in the application make side effect in him(got Head ache, BP get high/low, tension., etc). but unfortunately these side effects not bothered the development team., :( They are really worry about the quality of the product., but they show their worries in word not in work.
Tester:
The bugs which found in application, she doesn't waste her time and immediately show faults and clarifications exists in the application to the development team to make the fixes immediately., she worry about the quality and fear about the failure and transfer the same worry to management and development for to get some good things to happen.

Tester.., When you feel lucky..??

I felt lucky if i get blocker bugs in testing application means . :)
I felt more lucky if i found the bug even with in a hour after a new build, so that i reject the build, request development team for an new one to start test., :)

I don't think testers are lucky all the way., But My fellow tester in my team always said, Automation testers are more luckier than manual testers". I don think so how far it is true!. 

What are the types of software testers..?

This question is not yet asking by the interviewer yet., of course this is not an important question my dear software testing freshers., you no need to search Google to find answer for it.., :)
Am not having much experience in Software testing field, but in the couple of years, i come across numerable & memorable testers in the field.
Those guys make some important foot print in my way., I learned some good things which i have to follow., and some ones make me aware about certain things which i should not to do., I can easily differentiate those peoples in categories, Teasers and Taster, Testers.
Let me explain this category from last to first like stack: First of all, i would like to mentioned peoples comes under this 3 category are good at their testing work(Yes, good at their work in their views, In my point of view A Good Tester is the one who make the customer smile).
3) Teaser:
While he got the bug, one he started to laugh and celebrate otherwise, he got frustrate and started to fight with development team., Some times, people in this category is soft hearted means, they just started to cry, "Oh, My God dev team is not fixing my bugs'. like this.., :( They wont take any step to make the bug get fixed., Their full time work may be to glorify the application or otherwise to speck ill about the application., )
2) Taster:
They are test and find bugs and taste it., The bugs exists in the application make side effect in him(got Head ache, BP get high/low, tension., etc). but unfortunately these side effects not bothered the development team., :( They are really worry about the quality of the product., but they show their worries in word not in work.,
1)Tester:
The bugs which found the person make no reaction, she doenst waste her time to think like the silly ways, immediately show faults and clarifications exists in the application to the dev team to make the fixes immediately., she worry about the quality and fear about the failure and transfer the same worry to management and development for to get some good things to happen.

What a tester want?

As a tester i don know how many of you face this question., But in my experience i just expect every time this question from development team. But development team come to me with the answer not with question. the answer might be the project url, some documents or a KT.
As a tester i thought, i have a privilege to ask question about the anything what i do. but why the questions of mine always lead to the critical path.? :)
As a tester, in the testing community we all speck about plenty of testing methodologies, ideas, automation bla bla bla.., but what is actually happens in the organization, in to the team..? Is there any simplest way to apply the methodology recently i learn in the team? I can say loudly "NO"..., then As a tester, why do i still learn every day the new thing come today..?
As a tester i have a hope, flexible, and can able to test the thing what ever it may be., can able to give report.
As a tester, yes my questions some times make my team in to the dark path. But never go to stop this work of asking questions.. Because As a tester, i believe Faith cometh from Hearing, this is the one important quality of tester.Most of the time i wouldn't get answer for every question which i raise. But As a tester i never loose hope.Patient is the power of the tester who want to survive this industry.