tag:blogger.com,1999:blog-2405476812031211238.post967309113998654774..comments2023-07-12T18:09:56.569-04:00Comments on Rhythm of Testing: On Testers and Code Pete Walenhttp://www.blogger.com/profile/10651704389491850533noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-2405476812031211238.post-67999722887328915772014-07-28T10:15:53.604-04:002014-07-28T10:15:53.604-04:00Pete,
I can agree that not in all situations a per...Pete,<br />I can agree that not in all situations a person/tester should learn how to write code (programming). I think in our area of software there are basically 2 types of testers; Business oriented (understand the business logic and usage of target application) and Technical oriented (understand how the target application is built and how it interacts within the computer environment). <br />Both can learn to program, but it tends to be the more technical testers who do (and some can very well and others not so well). In regards to automation you get the people who are more technically oriented and also have some good programmer skills who do that work. <br />Either way though you need to have some solid 'testing' skills/knowledge to do this type of work. How you choose to do is up to the individual.<br />Key thing in the end is understanding how to talk to other people in other groups in their language. When talking to developers that may involve talking about code and how it is written (programmed). Having that skill and being able to do it well is a benefit to the tester in the end.<br /><br />Regards,<br /><br />Jim Hazen<br />Calkelpdiverhttps://www.blogger.com/profile/14278143481367031063noreply@blogger.com