Showing posts sorted by relevance for query bug reporting. Sort by date Show all posts
Showing posts sorted by relevance for query bug reporting. Sort by date Show all posts

Tuesday, 30 April 2013

Bug Reporting-Checklist


When you find a bug and when you want to report it to the developers or to the concerned people, make sure that the report you are sending is clear and are in understandable format. The bug report should help the developers to understand the history of the issues. Here is the checklist created for reporting the bugs.

1. Mention the environment (operating system).
2. Mention the browser you used along with the version
3.Mention the name of the reporter.
4.Mention the date
5. Summary: Summarize the bug. The summary should be short and meaning full. The summary should be able to explain the nature of the bug. Don’t exceed the summary like a paragraph.
6. Description: Here you can describe the issues. But make sure it should not be like an essay.Otherwise it would be like a story. Where the developer might get board to read or may not have time to go through entire description. Explain the risk in the description part.
7. Mention the severity.
8. Steps to reproduce: This is the best way to explain where the issue has occurred. This will help the developers to get into the specific place and help them to solve it.
9. Snapshot: Attachment is also a good way of representing the bug. This is also a proof saying that the issue has occurred. Because some bugs are non-reproducible. So,  in such case this would stand as a proof for those issues occurence. Good to send in .png format.
10. Give a meaning full name for the attachment
11. Check for the grammar mistakes and spelling mistakes.
12. Write the report in normal English word. Don’t use any complex words. So that developers may not Google it in search of getting meaning for those words.
13. Go through your report before you send it to the concerned people(if possible).

There are no standard template for the bug reporting. The reporting style varies from tester to tester.

“Writing a good bug report is a skill and it happens by practice"
                                                                                   - Pradeep Lingan

Saturday, 8 September 2012

A Few Tips for the Testing Fresher


                         
A Few Tips for the Testing Fresher 

      Here I wish to share some ideas for the fresher’s who want to start their career in testing.  Before getting into the real time work we just know testing is about writing the test cases, execute and if any bugs found we report it. But there are few more things to be considered beyond that. Most of us what we do is that we just learn the definition of testing, their types and so on. We feel that if we know the definition we know testing.  Knowing the definition that might help to some extend during some interviews, but not always.  Even in learning the definition, be aware that you choose the right material. Because there are “N” number of definition given for the question such as What is testing? The answer vary from people to people. Here I could say no body is best to give a perfect definition which could not satisfied by all. Because different people have different thoughts, unless you test you could not give a right definition.
Know the definition for the few questions that would be asked in interviews.
1.       What is testing & What is Software testing?
2.       Why testing ?
3.       Testing types
4.       Models
5.       Available tools
6.       Difference between Manual  & Automation Testing ?
7.       QA & QC ?
8.       Test case
9.       Test ides
10.   Test coverage
11.   Priority & Severity
12.   What is a bug ?
13.   Test scenarios
14.   STLC,SDLC Bug life cycle
15.   Verification & Validation

The above mentioned are the few questions that are frequently asked during interviews. The answer for the above mentioned question will be posted in my next blog. :-)

Now at work:

Most of the organization follows the scripted testing and some organization support exploratory testing. Scripted testing is what the organization totally depends on test case. They believe that if all the test case is executed and if all the condition is satisfied, then there is no bug in the application or product. This could help to few extend but not always. Because there are many product that failed in the production even after executing all the test cases. 




Exploratory testing:

     Here the approach is quite different. Here the testing is done without the test case.
 Remember not only the testers, but everybody do exploratory testing in real time. But we don’t realize. Exploratory comes not by training from some experts.  It’s an individual creativity.  For example think what we do when we buy a mobile phone.
 To be short the test we do while buying a mobile phone is a part of exploratory testing.

 Things I do while I follow the exploratory testing for a web application. This is how I start

1 .Know the purpose of that application
2. Know who are the end users
3. Explore it
4. Decide which I will be testing
5. Fix a time (Session based).
6. Be focused, because I consider I am responsible for the quality.
7. Give suggestion


My approach while testing

Most of the web application will have a login page . If I am going to test the login page, I consider the below mentioned points.

      The login page should have
1.       User name field   
2.       Password field   
3.       Forget password
4.       Login button
5.       Sign up option



Other things I Consider:
6.       User name field – rectangle shape ,(A-Z,a-z,0-9) ,boundary (min & max),special characters , check for empty space,
7.       Password field   - rectangle shape ,(A-Z,a-z,0-9) ,boundary (min & max),special characters , check for empty space
8.       Forget password-Hyperlinked
9.       Login button-enable/disable
10.   Sign up option- Hyperlinked
11.   Spell check
12.   Cursor at the right side of the Username  and password field
13.   Spaces between the fields
14.   Length of the password/Username
15.   Proper error message. User understandable form
16.   Highlighting where the error occurred
17.   Copy & paste the data in the field
18.   Data disappeared once submitting the wrong data
19.   Password in dot or * symbol
20.   Text entered should not exceed the rectangular field
21.   Check box-enable /disable
22.   Remember username/password are the mandatory field.So,  if no (*) symbol is provided it’s not an issue.
23.    Size of the font
24.   Color of the font and the background page color
25.   Font style.

The above mentioned things are the ideas that I consider and I do a mind-mapping so that I don’t miss any of those points .

            Okay now we tested an application and we found a bug .Now it’s our responsibility to report to a developer. How do we need to report? Here plays another major role which we call as “Bug Report”. Writing a good bug report is a skill.  The report explains the stuff of an individual. Here I share my ideas on writing the bug report.





Bug Reporting-Checklist

When you find a bug and when you want to report it to the developers or to the concerned people, make sure that the report you are sending should be clear and in understandable format. The bug report should help the developers to understand the issues by means of report you send. Here is the checklist created for reporting the bugs.
Ø  Mention the environment (operating system).
Ø  Mention the browser you used along with the version
Ø  Summary: Summarize the bug. The summary should be short and meaning full. The summary should be able to explain the nature of the bug. Don’t exceed the summary for more than 30 characters.
Ø  Description: Here you can describe the issues. But make sure it should not be like a paragraph.
Otherwise it would be like a story. Where the developer might get board to read or may not have time to go through entire description. Explain the risk in the description part
Ø  Mention the severity.
Ø  Steps to reproduce: This is the best way to explain where the issue has occurred. This will help the developers to get into the specific place and help them to solve it.
Ø  Snapshot: Attachment is also a good way of representing the bug. This is also a proof saying that the issue has occurred. Because some bugs are non-reproducible. So in such case this would stand as a proof for those   issues. Good to send in .png format.
Ø  Give a meaning full name for the attachment  
Ø  Check for the grammar mistakes and spelling mistakes.
Ø  Write the report in normal English word. Don’t use any complex words. So that developers may not Google it in search of getting meaning for those words.
Ø  Go through your report before you send it to the concerned people.


  “Writing a good bug report is a skill and it happens by practice “.
-Pradeep Lingan.













Friday, 22 November 2013

Testers Checklist-2

                                                                                                  
Here are the list that I have prepared for test enthusiasts to ponder over at the beginning of their testing career and those who have chosen software testing as a profession.


If you see software testing as not only your profession but a passion too, I hope this would be useful and you would have been following it probably.




1.      Communication:
When I mean communication most of us think about speaking/writing in English. Remember English is a language. There are some countries whose native language is not English. English could be a preferable choice if only the clients understand that language.Communication is the ability to communicate with all people. It could be in any language. In case of your project, if your are working for the US/UK/Australian clients then the medium of communication preferably will/can be English. It could be tough to learn some “X” language to communicate with the clients/ colleagues those who don’t speak English. In that case English would be better to manage for some extend. If you couldn’t able to catch up their languages, learn the language they prefer you to speak. But most of the Indian industries go with English because of clients they work for.


Speaking alone doesn’t come under communication skills, even writing too. Writing is another way of communicating with people. But this requires much more care when compared with speaking. Because writing doesn’t hold natural humans expression/Feelings. So, it could be misunderstood sometimes, for the people who are reading from the other end. So, have an extra effort in practicing writing more than speaking through word of mouth.


Let the audience decide if English is the most sorted language and if written is better or is oral communication as it is instance based and changes with the context.
Any communication is less or more depending on the who we are dealing with.
At times both written and oral communication is not sufficient. Non-verbal communication has its own place.


2.      Interest:
Interest would help the people to walk forward with more enthusiasm.  Rate of your career growth depends on the rate of your interest that you hold probably. Interest is an emotional feelings.It is like an engine that will help you keep moving in better way with love and joy. This could even make your life colorful. Because your profession is also associated with your personal feelings/life. So, find your interest that are in you and work with that. NOTE: You need to really work hard to find your interest that are in you.Because it is hidden always. Sometimes you may not find it throughout your life and you may miss your lovable life. So, I suggest you to sit calm and question to yourself to know more about you. This is one way of loving yourselves, your emotions/feelings.Many people have succeeded in their life, but only few people have become as a superstar in that concerned field because they are passionate about it. They would have learned about themselves more than anything else. Here are the list of some people who belongs to those list.


1. Sachin Tendulkar
2 .A.R. Rahman
3. James Marcus Bach
4. Pradeep Soundararajan
5. C.N. Rao
6. A.P.J.Abdul Kalam and many more


3.      Accept the Challenge:
Things( I would  say support, appreciations, Time and anything that you are more concerned about) that are nearby you will never be on your favor all times. Sometimes, it would hurt you as you never expected. Same, being in any profession you can’t relax with the role that you hold today. Tomorrow it may not be yours because of the competition world. So, ready to take up any challenges.Don’t be scared to learn and fear that you can’t do that.For the people who love challenges kudos to you. For the people who are bit scared I would suggest, you could go through some of the links that I have mentioned in the points 21.Hope  this might be helpful for you.


4.      Thinking Ability:
Thinking is another most important skill among the other that I have mentioned so far.When people ask about skills most of us don’t update thinking as a skill in our CV or in any profile that are shared in any social media. I personally feel that, How good your thinking is ,how your testing ideas/test cases are designed and this is how your testing probable be. So, improve the skills of thinking to make your testing better. This is another way that you will find  the difference among others.
5.      Courage to Listen:
Listen to the people whom you are speaking with or approaching. Allow them to speak to let you know their opinion on your decision.  It would be unfair, if you don’t have the courage to listen on your colleagues/ any concerned people ideas. And you might be on the wrong path, if you stick to your ideas without listening others opinion.


6.      Boldness to Speak :
Whatever you want to share you should be able to speak by facing their face. If you don’t have much courage to do that, you might be missing some points that are running in your heart/mind and you won’t express yourself in a better way as you expected. So, try to get rid of shyness, scaredness if you have such character.


7.      Share your Thoughts:
Share your thoughts with your colleagues. So, that they would probably share their thoughts with you. This would help you to learn much better sometimes or they may learn better from you.



8.      Know what Testing is :
The most important thing is to know what testing is than just going with some “X” document or following it blindly. Testing is not just following the document and reporting the job to the people. It cannot be called as testing. It can be called as checking. Because you are working based on someones command. Remember testing is different from checking. To check you need not think much. Because your job is documented in prior. But to test, yes, you need to think more. That is why I say thinking is most important skills a testers should have.


9.      Skills and Knowledge:
There is a difference between skills and knowledge. The things that you know and haven’t practiced yet, then it is knowledge. When you have practiced then it is a skill. Following document and applying it sometimes act as knowledge. No wonder,it could be test case/ design/ test ideas. When that is made by you then it is a skill.


10.  Programming Interest:
It is not that a tester who tests manually, shouldn't need of programming skills. It is good to know how to code. Choose the platform that you want to learn and have a good idea about it. So, that you would learn how to save time and how and when to automate.


11.  Social Media Connection:
Connectivity is an important for the testers. What you have learned from people would be shared among the four walls of your organizations. But engaging in social media would help you to connect with different people across the world. This would give you a platform to showcase your identity. So, make use of social media.


12.  Blogging:
Blogging could act as another way to improve, showcase ourselves. While blogging we will focus more on writing ability. This skills would be improving gradually. We would like to share the thoughts to ours .So, this will help us to know others feedback on your thoughts. We learn more, explore more to give a better results.


13.  Faking Result:
This is what one should not have thought career. Faking result, I mean saying “YES” to what all your Lead/ Manager says which doesn’t interest you and feeling that is a wrong one. To impress someone we should not fake ourselves. Be strong on your decision that you feel is right. If you want to impress others try to do that through your work, but not directly with the people.



14.  Bug Reporting:
Bug reporting is the proof to represent you and your testing.  To know more about bug reporting refer my blog post that I have published previously. It is a crucial skill a tester should be more aware of it and should be skilled about it. You could be very good in finding bugs and you have found some interesting bugs. But if your report is not good, I think it would be tough for you to express you and your work.  I have listed few things that would be helpful while writing bug report.




Here is the link that would be good enough to understand about reporting bugs and its importance.


15.  Presentation Skills:
A presentation skill is not only that you present your work to your boss/ colleagues or with any concerned people .It is also to learn how to represent ourselves with others. Representing could be our behaviour over different reactions. Presenting would include email writing,  handling sessions, body language, pronunciations.


16.  Don’t be a Blind Believer:
Don’t solely believe on the report that you got though some tools that you are using for testing. Sometimes tools would also produce inappropriate result. So, have a cross check once before you submit the report. Don’t blindly believe others. He/she may be well known in the industry. But it doesn’t mean that whatever they say will be correct at all times.


17.  Learn and Test:
Learn and test would be preferably suited for the people who know what testing is. People who depend only upon domain skills rather than testing skills may not follow this “learn and test” ideology all times.


18.  Follow People
Follow the people whose work interests you. If possible ask them to coach you. Learn from them and apply it in your own style. It is good to have a good coach for a better guidance in your career.


19.   Attending Conferences:
There are lots of conferences going on in many cities. So, attend the conference that you prefer it would be helpful for you to learn something new or better. At least be aware of conference that are happening in your places.


20.  Keep Practicing:
To me there is no term called an “Expert”. So, don’t have the mindset that you know many things or I am much experienced in something. The people whose names are most familiar in the world doesn't mean that they are experts, they are practicing and they don’t have the mindset of stop learning. They don’t say themselves as an expert because they know the meaning for it.


21.   Reading Books/Article:
You should have the passion to read books, articles of some great testers. It doesn’t mean that reading books/articles will help you to learn something related to testing Even a story books of some great leaders will help you to learn things that would  greatly helpful for your testing work. Here are the links of some article/books


            http://99tests.com/
            www.codecademy.com/‎
            http://testertested.blogspot.in/
            http://www.satisfice.com/
            http://www.testingcircus.com/
            http://chroniclesoftesting.blogspot.in/
            http://curioustester.blogspot.in/
            http://tuppad.com/blog/
            http://www.ministryoftesting.com
            
            


            1.Lessons learnt in software testing. - James Marcus Bach
            2.Are your lights on?- Don Gause ,Gerald M Weinberg
            3.Thinking fast and slow -Daniel Kahneman
            4.Testing computer software -Cem Kaner
             



22.Interaction:                              
Interaction is most important for any professionals. you could interact with different people through social media, people in your office. This will help you to learn more from different people.


23.  Being  Honest:
Be honest in your report(bug report, status report, experience report) that you send, the words that you share.
When you fake your thoughts, no more you will have the passion to learn and your growth would slip from the ladder step by step without your knowledge. So,Be honest to yourself.


24. Certification Vs value:
To know much about certification please look into this link. I hope this will help you understand how to approach when preferring certifications.




25.Tools knowledge:
Tools are the another important source to test the product. it could give result as fast as human do. So, it is good to know the tools that are required to test based on its types. But remember it doesn’t mean that tools give the accurate result all times. It is also a software where there could be an existence of the bug. So, have a cross check over that tool. There are “N” number of tools available in the market. To pick up the best among the existing tools would be your skills. To know much about some tools here is the link


26.Updates about  latest technology:
Learn the latest release of the softwares. One should be updated that with the changes
happening in the technology.


27.Mentorship:
Mentors are the teachers. Being a starter it is good to find the person who could guide you in the best way. whom you believe that he/she would show you the right path. Yes, it is important to analyze before confirming. If the teacher is in wrong path. the follower also would move in the same. Be aware of that.


28.Setting Principles:
Have the principles of your own.and don’t have the habit of bow your head for any case. Have a principle and try to follow that and try to be a model to others


29.Research:
It depends on the interest. You could get into the research about your learning. This would help you to understand your job better and help others to know about your passion.


30.Participating events:
There are “N” number of events conducted related to software testing. It is good if you participate those events and make sure those events are worth enough to attend. The events are conducted all over the world.

31.Working on plans:
It is one of the important thing a professional should do, One should have to plan for improving his/her skills sets. The right plan would take you to the right path, if your focus is really on that plan. So plan for the day/month/year and try to follow it strictly.
If your focus is clear then your path is clear


32.Questioning :
If you look into the definition of testing that I have written, hope you understand the need of
questioning. Questioning is what a part of  testing is. You learn a lot by questioning yourself and others. It is one of the most important skill set a tester should have throughout his/her career.




You are not a Scientist, but you have to think like a scientist
You are not a Judge, but you should be good in making decision
You are not an Astrologer, but you should be able to predict the products behaviour


“YOU” are now a software tester. Yes, you should have the attributes of all these and more.


     
I sincerely thank "Jyothi Rangaiah" for her supporting hands.



Thank you






Your feedbacks are most welcome



My Contact Details:


E-mail: ktg.pradeep@gmail.com
Phone: 07639959901
Skype: pradeep.lingan