Entries Tagged 'Tester vs Developer' ↓

Again, I want to share my experiences with you on an interesting software testing topic. It’s a hot topic in any organization, yes as a tester or QA you can guess it, nothing other than – Testers vs. Developers.

Testers the troublemakers

It’s funny, how almost everywhere developers consider testers as the troublemakers. Actually it’s not their fault, no one like to hear faults in his/her own baby. And same thing which we (tester) are doing, of course intention behind that is to deliver quality output to client. Constantly there is bitterness at some point in the game between these two roles. Wonder why? It’s the genre and responsibility of these two roles.

Continue reading →

This article is by Pradeep Soundararajan, our guest author at SoftwareTestingHelp.

Many thousands of software testers I came across had the notion that they are into testing and are solely responsible for quality. Some of them even think that being a tester also empowers them as a God of Quality for the product.

The questions I ask you is: Is this for good?

Here is what I think and would like to see you considering these ideas.

Quality is everyone’s responsibility and not just a tester out there or thousands of them out there. If your family has to be happy, you can’t assign a person in your family as ensurer of happiness and catch the ensurer responsible if something goes wrong. If a family has to be happy forever, it has to happen with everyone participating and facilitating it.

Continue reading →

This can be a big debate. Developers testing their own code – what will be the testing output? All happy endings! Yes, the person who develops the code generally sees only happy paths of the product and don’t want to go in much details.

The main concern of developer testing is – misunderstanding of requirements. If requirements are misunderstood by developer then no matter at what depth developer test the application, he will never find the error. The first place where the bug gets introduced will remain till end, as developer will see it as functionality.

Continue reading →

Software Testing has lot of challenges both in manual as well as in automation. Generally in manual testing scenario developers through the build to test team assuming the responsible test team or tester will pick the build and will come to ask what the build is about? This is the case in organizations not following so-called ‘processes’. Tester is the middleman between developing team and the customers, handling the pressure from both the sides. And I assume most of our readers are smart enough to handle this pressure. Aren’t you?

This is not the case always. Some times testers may add complications in testing process due to their unskilled way of working. In this post I have added most of the testing challenges created due to testing staff, developing staff, testing processes and wrong management decisions.

So here we go with the top challenges:

Continue reading →

Recently I read a very interesting article on “All I Ever need to know about testing” by Lee Copeland.
I was so impressed with the concept of our day to day work comparison with the software testing.

I will extract only points related to software testing. As a software tester keep in mind these simple points:

Continue reading →

It’s a every testers question. How to be a good tester? Apart from the technical knowledge, testing skills, tester should have some personal level skills which will help them to build a good rapport in the testing team.

What are these abilities , skills which make a tester as a good tester? Well, I was reading Dave Whalen’s article “Ugly Baby Syndrome!” and found it very interesting. Dave compared software developers with the parents who deliver a baby (software) with countless efforts. Naturally the product managers, architectures, Continue reading →