hair-pulling frustration

[J. Landman Gay]

On 11/11/2014, 3:16 PM, Richard Gaskin wrote:
> So while we can't be expected to test everything, if we only test our
> own apps with new builds that's usually all we need for our own work.
> Collectively, if we call just ensured that new features get implemented
> in ways we need, we'll all have what we want.

If it's easy to report a bug, I do it. The lack of command key 
functionality for example. I can just describe a procedure to follow. 
Demonstrating a problem with an image redraw is easy and only requires a 
single card with an image and a few lines of script. I jump on that sort 
of thing right away.

What usually stops me is the need to create a separate, stripped-down 
stack to demonstrate a more complicated bug. I completely understand the 
need for this, especially in my case where the original stack is huge 
and complex, and I wouldn't expect RR to plow through all that. But 
extracting the exact set of circumstances that reproduce the problem 
without including all the surrounding code can sometimes be a whole 
afternoon's work or more, so I don't do it. I just hope someone else has 
a simpler example and will report it for me instead.

I know when I do this that I'm not helping myself very much, but there's 
too much going on to do otherwise.

-- 
Jacqueline Landman Gay         |     jacque at hyperactivesw.com
HyperActive Software           |     http://www.hyperactivesw.com