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