{"id":110,"date":"2007-06-12T12:03:55","date_gmt":"2007-06-12T12:03:55","guid":{"rendered":"http:\/\/quinert.com\/blog\/xml-rss2.php?itemid=39"},"modified":"2007-06-12T12:03:55","modified_gmt":"2007-06-12T12:03:55","slug":"more-on-dev-tester-relations","status":"publish","type":"post","link":"http:\/\/www.software-testing.com.au\/blog\/2007\/06\/12\/more-on-dev-tester-relations\/","title":{"rendered":"More on dev-tester relations"},"content":{"rendered":"

Matt Heusser<\/a> has continued discussion of tester-developer relations<\/a>, where Jonathan Kohl<\/a> describes the flipside of testers telling developer’s that their automation code sucks.<\/p>\n

Actually there are many scenarios, derived from at least a few properties –<\/p>\n

– Does the person doing the automation know\/not know that their code sucks.
\n– Is the code ‘suckage’ pointed out by a third party, or the person writing it.
\n– Is the automation being done by a tester or a developer?<\/p>\n

You can plot these out as a truth table and see where you fit. I tend to be automating, saying “I would love some help with this”, but can’t get help or chances to pair with developers. I’ve also observed testers wanting to pair with developers, but developers not wanting to come down to the tester’s skill level or work with their tools (as well as the case I mentioned in my previous post).<\/p>\n

I’m sure situations also exist where the testers aren’t interested in working with the developers and learning.<\/p>\n

So we have a model that contains –<\/p>\n

– the feedback
\n– the source of the feedback
\n– awareness of the current state
\n– receptiveness to feedback
\n– desire or ability of one of the parties to change the situation.<\/p>\n

Has anyone experienced any of the other permutations of these properties?<\/p>\n","protected":false},"excerpt":{"rendered":"

Matt Heusser has continued discussion of tester-developer relations, where Jonathan Kohl describes the flipside of testers telling developer’s that their automation code sucks. Actually there are many scenarios, derived from at least a few properties – – Does the person doing the automation know\/not know that their code sucks. – Is the code ‘suckage’ pointed […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3,29,30,33],"tags":[],"class_list":["post-110","post","type-post","status-publish","format-standard","hentry","category-agile","category-software-development","category-software-testing","category-teamwork"],"_links":{"self":[{"href":"http:\/\/www.software-testing.com.au\/blog\/wp-json\/wp\/v2\/posts\/110","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.software-testing.com.au\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.software-testing.com.au\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.software-testing.com.au\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.software-testing.com.au\/blog\/wp-json\/wp\/v2\/comments?post=110"}],"version-history":[{"count":0,"href":"http:\/\/www.software-testing.com.au\/blog\/wp-json\/wp\/v2\/posts\/110\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.software-testing.com.au\/blog\/wp-json\/wp\/v2\/media?parent=110"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.software-testing.com.au\/blog\/wp-json\/wp\/v2\/categories?post=110"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.software-testing.com.au\/blog\/wp-json\/wp\/v2\/tags?post=110"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}