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

Monday 29 April 2013

How the testers should be?


These are the checklist I have provided hope that holds good if tester has certain qualities.
1. Testers are not a scientist but they should think like a scientist
2. Tester should perform a test by considering him/her as an end users
3. Play an end users role. This will tell you the product usability
4. Testers should develop a thinking style (thinking skills). Thinking style means creative thinking
5. Testers should be a good analyzer. He/she should be good in analyzing the product. This helps him/her to judge the risk on looking at the requirement document.
6. Testers are not a judge, so don’t give the final judgment.
7. Testers should have the passion of listening on others comments.
8. Testers should be a friendly to the developers (support to the developers) and also to the concerned people, friendly doesn't mean that you should be compromised on reporting the bugs.
9. Keep questioning a product until you understand the scope of the project.
10. Testers should listen and then react.
11. Good reviewers
12. Smart enough in bug reporting
13. Smart in making test ideas
14. Ready to explain the product at any stage .So learn about the product before you test.
15. Work for the quality
16. Not a narrow minded
17. Accepts the suggestion made by others
18. Testers should be a good investigators
19. Share the ideas and learn from others
20. Constant learning about the product
21. Take up the challenge.



My Book:
Bug Hunter- A Testing Guide for a Beginner.

My Contact Information:
Phone: 07639959901
E-Mail: ktg.pradeep@gmail.com
Face book: pradeep.lingan.1@facebook.com
Twitter: pradeeplingan1
Skype: pradeep.lingan

Thursday 11 April 2013

My 1 Year Journey as a Software Tester

How I chosen Testing as my career:
It's a common among the (most) fresh passed out student, after completion of my graduation I started searching for the job. It was a recession time (2009). Very few (less than 1 % approx up to my knowledge) opportunities are there for freshers in very few companies. I didn't get through in any of those companies. So, I decided to do some certification. But, the question in my mind was what courses to choose? As, my uncle Ganesh Pathan (who is working as a Developer in I|Nautix) advised me to do a Java Certification. I don't have much idea about programming before joining the course. At the completion of my course I got few opportunities to attend for the interview for the developer positions. But I didn't get through. The reason was I didn't study with interest. My focus was to get a job. No matter what sort of job, or company, package. I need some job. That was the only thing running on in my mind.
After few days I joined in one BPO, I worked there for few months, But I don't want to continue with that work. There was a lead who doesn't know how to treat his colleagues. He treats his colleagues as school students. He taught (Sorry I learned) me how a team leader should not be.
I know, I can't share or improve my skills in this job. I wished to work in a technical part. Again, I started to search for the job. I could get only in the BPO's not in some software companies. My Parents were much worried about my career. But, still they never put me on pressure as some people do normally. They helped me to get a job where I can be stable (I mean work not in a company) and there was a great support from my elder sister and my uncle. They helped me a lot in getting a job. Again, I decided to do some certification course. I asked my uncle for that. He suggested me to do testing as there was a demand for that.
So, I was looking for the training center. My friend "Ganesh prasad" told me about "Tes pro", Chennai. I was surprised to see a tester started a training institute to educate a freshers in Testing. I had a great time with the Testers “Mr. Murali Jayraman and Mr. Partha Sarathy" and my staff " Mrs. Lalitha and Mrs. Sangeetha.
They provided some job opportunities (Interview in some companies), I failed again.Then I went to Bangalore for searching jobs. I was in my friend’s room. One of my friend Murali perumal who is working as a Software tester helped me in some ways to get a job. But that didn't work out well.

The beauty of Tes pro Training institute:
I see and heard some institute who hire people for their business sake. They convince people to join in their institution. They normally make this promise (100% placement with few, some time more company names). But the Tes pro is quite different, they used to say the current market standard and how for the candidate is eligible (passed out, percentage, etc. ) in getting a job. They speak the truth and even after completing the course they still remember people and provide an opportunity in getting a job. They do their best for their students.
The another beauty is after getting a job, if the candidate is not interested in that work or companies, they still consider the candidate profile and provide an opportunities where most of the institution don't do that
.
My First Software Company:
One day I got a call from Tes pro about the opening in "Moolya ". Thank God I got job In Moolya. I thank "Tes pro" for providing this opportunity to me. I joined Moolya in 12th April as a Junior Software Tester". I was scared first by seeing the people there. Then after few days I got adopted to their environment. I was amazed to see some of the testers there and their work culture that impressed me more. Till I joined in Moolya I had no idea about being a passion at work. But after seeing some testers there, I learned what passion is! Every day I learn something from them and somehow I was trying to be like them. Then I decided that testing as my long term career and I was more comfortable with the work I did and am doing right now. I see people writes a blog, attending conference and lot more.So after a few months, I started writing blogs with the support of few Moolyawans. I always thankful to those colleagues (especially Yagnesh and Manju) who encouraged me in writing blog.

I listed the things what I have learned in this one year.
1. Writing blogs
2. Testing Open source projects during free time.
3. Writing bug reports.
4. Writing books.
5. Debate with testers on some topics through social media.
6. Behaviour (the most important skills a professional must have)
7. Confidence in facing the challenge
8. Shown my identity with the help of some social network
9. Taking a session for the fresher (college pass out students)
10. Automation tools (Scripting skills).
Some of the list mentioned above is just because of the testers especially “Mr. Pradeep Soundararajan" and “Mrs. Parimala Hariprasad" who taught me what passion is!. They are my inspiration too.
In January 2013, I joined in another start-up "Mindzpark Technologies", Coimbatore. I was quite happy with the work environment and also with the people who are working there. I am happy to see even a higher official like CEO and Managers listening to my ideas and suggestion. It's not as easy in some companies. I realized this would be another good place to work. Thanks to my friend Sakthivel (Software Developer @ MIndzpark) who helped me in getting this job.
Now, I am handling multiple projects as I am the only tester here and also proud to say that I am the first tester of Mindzpark. I have learned some tools and implemented it to the work.

My Journey in "Mindzpark Technologies”:
Here in Mindzpark , we are a service providers and also a product based. The recent product we worked and launched is "Catalog Bazaar". How I played a role in this project? I and two developers were worked on this project. I do a testing, I give some new suggestion and explain the risk on certain features helping the developers to know the module coverage and supported in many ways. I know testing is about encouraging a product. Though with some pain(as normally a professional face during the dead line ), we worked overnight on those last week and we finally launched this website. I realized the successful completion for this work, is just because of the mutual understanding between me and the development team. I learned that the good understanding in a team will give a good result.

Love your Job, not an Organization.
You can't make the organization as your stable (friendly) company. You can be fired and again re-hired, and lot more. But it is not in the case of your job. You can't trust the organization for some things but you could do it for your work. I thank God for providing an opportunity to know my mistakes and get corrected from it and also for facing some problems in very short time.
I least bother about an organization (Company where ever I work) decision like (Fire, appraisal etc on (me). I just go ahead with my style of work.
There are some people where I am always thankful to them
I thank my Parents, God, my Sister and my Uncle, Friends, colleagues. Hope at the completion of my second year journey in my testing career, I would come up with some more new skill set and ideas in different style.
I don't commit all the mistakes purposely. But I love to learn and get corrected from the mistakes. I believe that “The lessons learned from the mistakes are worth more than the the one I know already”.

Thank You All!!!

My Book:
Bug Hunter- A Testing Guide for a Beginner.

My Contact Information:
Phone: 07639959901
E-Mail: ktg.pradeep@gmail.com
Facebook: pradeep.lingan.1@facebook.com
Twitter: pradeeplingan1
Skype: pradeep.lingan