Entries Tagged 'Tester vs Developer' ↓

Why Software Testing is a Tough Job? And Here is How You Can Make It Easy

You are so lucky to be in testing, you won’t have to look after all these messy things – prototyping, client confirmation, development, logic.., – a frustrated developer

But I have to look after mess you create, – a frustrated tester

A long silence.

Most of the time, being in testing industry, we have felt mixed emotions – at a time it seems really easy and at a time it feels really difficult.

Continue reading →

10 Reasons Why Your Bugs are Getting Rejected and What You Can Do for it as a Tester!

I am not going to spare her. She has rejected 7 bugs, I reported, within last three days. I know she is using personal grudges as professional sword……

------------

A team mate was fuming and the discussion suddenly caught fire when couple of other team mates joined in sharing same experience with other developers. The team meeting turned a discussion point about bug rejection. After some discussion, we all decided to do a simple exercise to save ourselves from the humiliation of bug rejected, in future.

Continue reading →

Is Software Tester’s Job Really a Low-profile Job?

Software Tester’s Job – Is it really as low-profile as it is believed to be?

Sometimes, the decision to become a software tester is not deliberate for some of us, especially in the beginning of our careers.

Though the aspiration for being a successful IT professional is strong, we assume that the word ‘IT professional’ is synonymous with ‘Developer’. While being a developer is great and has immense potential, it should not be concluded that being a tester means the exact opposite.

software testing job myths

Continue reading →



What is the Best Way to Make Developer and QA Relationship Healthy?

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 →

Fake God of Quality versus True Humans – Who is responsible for Software Quality?

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 →

Developers are not good testers. What you say?

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.

Optimistic developers – Yes, I wrote the code and I am confident it’s working properly. No need to test this path, no need to test that path, as I know it’s working properly. And right here developers skip the bugs.

Developer vs Tester: Developer always wants to see his code working properly. So he will test it to check if it’s working correctly. But you know why tester will test the application? To make it fail in any way, and tester surely will test how application is not working correctly. This is the main difference in developer testing and tester testing.

Should developers test their own work?

Test in progressI personally don’t mind developers testing their own code. After all it’s there baby ;-) They know their code very well. They know what are the traps in their codes. Where it can fail, where to concentrate more, which is important path of the application. Developer can do unit testing very well and can effectively identify boundary cases. (Image credit)

This is all applicable to a developer who is a good tester! But most of the developers consider testing as painful job, even they know the system well, due to their negligence they tend to skip many testing  paths, as it’s a very painful experience for them. If developers find any errors in their code in unit testing then it’s comparatively easier to fix, as the code is fresh to them, rather than getting the bug from testers after two-three days. But this only possible if the developer is interested in doing that much testing.

It’s testers responsibility to make sure each and every path is tested or not. Testers should ideally give importance to all small possible details to verify application is not breaking anywhere.

Developers, please don’t review your own code. Generally you will overlook the issues in your code. So give it to others for review.

Everyone is having specialization in particular subject. Developers generally think how to develop the application on the other hand testers think how the end user is going to use the application.

Conclusion

So in short there is no problem if developers are doing the basic unit testing and basic verification testing. Developers can test few exceptional conditions they know are critical and should not be missed. But there are some great testers out there. Through the build to test team. Don’t waste your time as well. For success of any project there should be independent testing team validating your applications. After all it’s our (testers) responsibility to make the ‘baby’ smarter!!

What you say?