Entries Tagged 'Career in Software Testing' ↓
June 27th, 2016 — Career in Software Testing, Tester vs Developer
Being in the QA field for 9 years now, I have seen that some people generally stay away from a testing job. They feel inferior and have a lot of negative thoughts running through their minds.
I would like to share my thoughts and experience and address some common myths that people have.
Myths about being a Software Tester: Continue reading →
May 26th, 2016 — Career in Software Testing, Testing best practices, Testing Tips and resources
We all heard the story of the little frogs in the well who thought the world is the well until they came out and realized how big, beautiful and different it is!
Do you think you have lived this story at some point in your professional life? Well, everyone has. Welcome to the world of reality – beautiful testing :).
Today, I want to share 4 mistakes I made when I started my software testing career. You’re Probably Making These. Check out. Continue reading →
May 2nd, 2016 — Career in Software Testing, How to be a good tester
There is always room for improvement and making things better.
If starting as a QA fresher and spending a few years in the field have not changed you from tester to a Good/Great tester, this article is for you. Read on –
Testing, reporting, and finishing a task is something anyone can do after a while with experience and training. But, being a tester is so much more. Continue reading →
April 28th, 2016 — Career in Software Testing, Software Testing Resume
Do you know that employer spend only 20 to 30 seconds to review your resume? To get it noticed in such a short time frame your resume must be appealing, organized, and error free.
Today’s article is about refining your resume so it finds you your dream job.
Here are a few guidelines that will make your resume stand out from the crowd:
Continue reading →
April 21st, 2016 — Career in Software Testing, How to be a good tester
How To Be a Bold and Confident Software Tester:
“The issues are almost similar. Mark them duplicate”, says Person 1 (you can tell, it is a developer)
“No, they are not. They impact different areas of the application. Behavioral impact is different too”, argues Person 2 (of course, it is a tester)
“Your team is only interested in increasing bug count”, retorts Person 1.
“Actually, we are trying to reduce it”, Person 2 counters.
Isn’t this a common scenario in every organization?
Continue reading →