2,354 reputation
1614
bio website dhemery.com
location Sacramento, CA
age 55
visits member for 3 years, 3 months
seen 4 hours ago

I consult, write, and speak about leadership, software development, testing, test automation, and resistance to change.


Dec
31
awarded  Good Answer
Dec
29
reviewed Approve suggested edit on Test Strategy Documentation
Nov
26
reviewed Edit suggested edit on Running Selenium webdriver scripts in android device (Samsung galaxy tab)-Portrait mode
Nov
26
revised Running Selenium webdriver scripts in android device (Samsung galaxy tab)-Portrait mode
typo in title
Nov
16
reviewed Approve suggested edit on Selenium 2 RemoteWebDriver constructor error: java.lang.String cannot be cast to java.util.Map
Nov
16
reviewed Approve suggested edit on What measures do you use to assess software quality?
Nov
16
reviewed Approve suggested edit on How to use AutoIT for handling multiple authentication windows with different credentials?
Nov
4
reviewed Reject suggested edit on Selenium error in NUnit C#
Oct
29
reviewed Approve suggested edit on How to save compiled document on Desktop using C# Selenium
Oct
26
reviewed Approve suggested edit on Selecting items in a combobox using Webdriver
Oct
18
answered What manual testing should be done when no time for automating it?
Oct
16
answered What are the main goals of “Automated Testing”?
Oct
15
reviewed Approve suggested edit on Selenium Webdriver Mobile with Python - AndroidWebdriver4Python installation question
Sep
30
reviewed Reject suggested edit on Good Grep Tools for Windows
Sep
28
comment How to prevent cheating by manual testers?
Well, they might not need to test, depending on the information he needs. But if he needs information that can come only from testing, they'll have to test in order to create the information. But my point is: Don't ask them for the work. Ask them for the valuable result. It's easier to tell whether you're getting it. And they'll better understand the value of what you're asking for, which may offer better motivation than sticks and game-able metrics.
Sep
28
answered How to prevent cheating by manual testers?
Sep
23
answered Fixes hard to verify because of poor quality bug reports
Sep
22
awarded  Custodian
Sep
22
reviewed Approve suggested edit on source-control tag wiki excerpt
Sep
13
comment Test data specification to generate actual test data
Ah, I see I misunderstood the thrust of the question. I don't have a name for the shift you made. I just keep applying two principles: 1. Name every important idea. 2. Hide incidental details. Easier said than done, given the slippery words important and incidental, but you seem to have an unusually good grasp of those ideas.