Comments on: 8 Ways to be a Good Software Tester

By: Devon Smith

Devon Smith — Mon, 22 Feb 2010 17:31:54 +0000

Great post! These points serve as an excellent reminder on the value of staying active and engaged in with your work.

By: Able Weis

Able Weis — Mon, 15 Feb 2010 11:16:40 +0000

9 th way to be a good software tester is to grab a certification in software testing. After having certified over 38,000 professionals in 43 countries and setting standards for software testing practitioner certifications, QAI has launched a new manager level certification for Software Testers called Certified Manager of Software Testing (CMST) – http://bit.ly/qaistp

By: 7 Ways To Be Good Developer From Tester Point of View | Test And Try

7 Ways To Be Good Developer From Tester Point of View | Test And Try — Wed, 29 Apr 2009 12:24:39 +0000

[...] days ago I wrote how to be a good tester, now try to identify points that are important for the developer from tester but also the quality [...]

By: Marcin Zręda

Marcin Zręda — Thu, 16 Apr 2009 07:24:36 +0000

Hi Akshay: Thanks for comment.
“Live in accordane” means don’t blame each other at all. You are right that live too close is not so good. Of course report bugs to BugTracker not to developer ear. Generally have a good relationship with developers but bear in mind that You are the Tester and You must find as manny bugs as possible :)

By: Akshay

Akshay — Thu, 16 Apr 2009 04:31:11 +0000

Your points are good. But I would like to comment on number 5 on the menu. I would never allow a tester to team up with a developer, for some very strong reasons. First of all, this may adversely impact the amount of bugs opened. Issues may be communicated verbally, rather than by email… I know that the ultimate goal is to make good software, so this should not matter, but another goal is to make sure everyone is doing his/her job right. More bugs usually means, the dev guys are incompetent or merely slacking off (forgive me for being blunt… but that is just the way it is… ). So if bugs are communicated verbally, there is no record of these issues. Secondly, there is a chance that knowingly or unknowingly, the developer gives the tester a happy path into the application. This is totally unacceptable from the usability point of view. The less testers know, the better. Hence non-techies sometimes make the best testers. If there are communication gaps, what are the managers for? let them fill the communication part in. Let the testers stick to testing. And reporting the number of errors per developer is not only good practice, it should be standard practice. The JOB of the developer is to give good results. That is what they are paid for. It is like saying, don’t judge Bush for the mistakes he committed in his presidency. That was his job. I also firmly believe that testers should be judged on the amount of bugs they open. Because, that is their job. It is a harsh world man… what can I say.

By: Www Test

Www Test — Wed, 15 Apr 2009 06:26:35 +0000

[...] Test 8 Ways to be a Good Software Tester Test And Try I found some cool stuff here: 8 Ways to be a Good Software Tester Test And [...]