tag:blogger.com,1999:blog-5166487924843918388.post2393833217529456728..comments2023-10-24T09:17:42.258-04:00Comments on Peak Performance: 10 Things About Testing That Should DieAnonymoushttp://www.blogger.com/profile/11678206907629678117noreply@blogger.comBlogger11125tag:blogger.com,1999:blog-5166487924843918388.post-62852852417386716572012-07-26T10:59:31.532-04:002012-07-26T10:59:31.532-04:00Is it bad that I yelled laughed and yelled "s...Is it bad that I yelled laughed and yelled "so true ..." at the screen as I read this? Thank you! :)Michelle Mnoreply@blogger.comtag:blogger.com,1999:blog-5166487924843918388.post-12330549208253725182011-12-23T11:40:32.712-05:002011-12-23T11:40:32.712-05:00Good and agreed on points Scott but it kind of con...Good and agreed on points Scott but it kind of concerns me a post like this is needed in the first place.<br /><br />I guess it's good to lay them out.Tony Brucehttps://www.blogger.com/profile/14044205740382054059noreply@blogger.comtag:blogger.com,1999:blog-5166487924843918388.post-34819245310711706342011-12-06T13:44:23.641-05:002011-12-06T13:44:23.641-05:00Love this post.
As you mentioned that "teste...Love this post.<br /><br />As you mentioned that "testers communicate bugs verbally and dev team fix the bugs quickly on testing environment.<br /><br /> But what if developers keep making changes on testing environment but it might break other working areas if changes are done in hurry..Sumitnoreply@blogger.comtag:blogger.com,1999:blog-5166487924843918388.post-54166194886617202962011-12-04T16:57:11.862-05:002011-12-04T16:57:11.862-05:00Liked the last one (point 1) :)Liked the last one (point 1) :)Testing Tools Journalhttp://www.toolsjournal.com/testingblognoreply@blogger.comtag:blogger.com,1999:blog-5166487924843918388.post-70848360229932506202011-12-03T02:24:36.770-05:002011-12-03T02:24:36.770-05:00TestSheep,
Yes, it is your job to make the right ...TestSheep,<br /><br />Yes, it is your job to make the right people aware of things you feel are important (as well as things you feel *should* be important to them). The difference between that and egocentricity is the understanding that it is *their* job, not yours, to make the decision about what to do with that information.<br /><br />They have (or at least *should* have) information that you don't, which means that sometimes they will make perfectly correct and appropriate decisions that seem completely nonsensical and idiotic based on the information we have.<br /><br />The best we can do is ensure that folks have and understand the best information available upon which to base their decisions and then accept the decisions they make.<br /><br />If they regularly make decisions that are unacceptable by your standards, and those decisions are supported by their peers and superiors, that is a good indicator that you are not employed by a company that is a good fit for you culturally & that it may be time to look for a new employer. "Whining and gnashing of teeth" will do nothing other than lead to folks listening to you less, not more... at least in my experience.Anonymoushttps://www.blogger.com/profile/11678206907629678117noreply@blogger.comtag:blogger.com,1999:blog-5166487924843918388.post-52672017253630432012011-12-02T23:18:02.952-05:002011-12-02T23:18:02.952-05:00I enjoyed this article. Thanks!I enjoyed this article. Thanks!Debrichhttps://www.blogger.com/profile/05875011470811214203noreply@blogger.comtag:blogger.com,1999:blog-5166487924843918388.post-36639999787779489242011-12-02T22:20:39.887-05:002011-12-02T22:20:39.887-05:00There is definitely something between elements 10 ...There is definitely something between elements 10 and 9 which strikes a bit of a chord.<br /><br />"You are a service provider and your primary clients are the managers" ...<br /><br />I've worked as both a consultant to a project, and as a permie within project group. It's certainly a lot easier to be dispassionate as a consultant.<br /><br />Esp when projects are being steered through technical decisions by project members like marketing etc who are least technically skilled to make those decisions, it's hard to "sit back".<br /><br />As a professional, you are supposed to use your experience to try and keep a project from steering itself into rocks. That's not egocentric, it's an actual commitment to the customer.<br /><br />Sometimes your job in supporting the business owner is to protect the business owner from the business owner - esp when they are given to making too many change, arbitary decisions (with big impacts to the project) etc ...TestSheephttps://www.blogger.com/profile/05047308702049182716noreply@blogger.comtag:blogger.com,1999:blog-5166487924843918388.post-48034984738386075062011-12-02T21:47:58.376-05:002011-12-02T21:47:58.376-05:00Fantastic post Scott. I agree with the comments o...Fantastic post Scott. I agree with the comments on Twitter that this could easily be a great conference session or a really great keynote.<br /><br />I've struggled with encounters on almost all of these elements over the years but 4 and 7 really seem to follow wherever I may travel. They're first on my hit list at any place I find myself working :)gMasnicahttps://www.blogger.com/profile/17322470410579466327noreply@blogger.comtag:blogger.com,1999:blog-5166487924843918388.post-76164372088015339382011-12-01T16:21:43.061-05:002011-12-01T16:21:43.061-05:00Via twitter, a comment:
It might be interesting t...Via twitter, a comment:<br /><br />It might be interesting to describe the anti-pattern.<br /><br />I wonder what I would see, hear, feel when I visited for a week - an organization with all ten behaviors?Griffin Joneshttps://www.blogger.com/profile/08610930934130482071noreply@blogger.comtag:blogger.com,1999:blog-5166487924843918388.post-29729105862527812422011-12-01T13:03:05.982-05:002011-12-01T13:03:05.982-05:00Thanks Sean!
I have encountered this same issue ...Thanks Sean! <br /><br />I have encountered this same issue - which is actually why I advocate against a test phase; HOWEVER, you are correct that simply eliminating the test phase does not solve this problem. Close collaboration (or as you put it "proper communication") is necessary to avoid this situation.<br /><br />I'd argue, based on my experience, that *if* the developers and testers are working closely together that this wouldn't occur because:<br /><br />- The dev would have test assessing what they've done *prior* to merging it into the main branch of source.<br /><br />- The tester would be doing their "initial" round of testing paired w/ the dev (or at least in very close collaboration), so that the issues are "reported" immediately and verbally -- and only logged in the tracking system if those issues will not be dealt with immediately.<br /><br />Again, this concept demands a mature degree of teamwork where members of the team do not need micromanagement (which I think ought to be a goal of all teams, but I recognize that not all teams will be successful).<br /><br />I think that might be a "unifying point" here. I get that not every team will start, or even successfully mature, to be able to implement these concepts effectively. But that should, in no way, be taken as an excuse for the industry to lower the bar & accept mediocrity (or micromanagement) as the desired end-state of their team's evolution.Anonymoushttps://www.blogger.com/profile/11678206907629678117noreply@blogger.comtag:blogger.com,1999:blog-5166487924843918388.post-84038140611519341132011-12-01T12:10:11.072-05:002011-12-01T12:10:11.072-05:00There are a lot of good points here (at least 10 :...There are a lot of good points here (at least 10 :). But I do have a comment on 4. Testing Phase. I agree with much of what you say. But a problem we have had to deal with is when a tester starts testing a feature and reports a bunch of issues, only to have the developer say "yeah, I'm not quite done with that feature." Worst case the developer declares these bug reports invalid and the tester has to redo everything they already did. Hence management requires a "release to test" flag, sort of like a test phase. This can be improved with the proper communication. If the developer says "I'm done with the import, but still have to work on the reporting" for example, then the tester can get a legitimate start. Looser "rules" require better communication.Seanhttps://www.blogger.com/profile/03140483115837815459noreply@blogger.com