"Excellent testing is a rich and open-ended intellectual activity. It cannot be encapsulated into discrete procedural units."-James Bash

Thursday, 12 December 2013

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? :)

Tuesday, 3 December 2013

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 :) )

Monday, 18 November 2013

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

Wednesday, 4 September 2013

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!. 

Monday, 12 August 2013

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.