On Wed, Dec 22, 2010 at 11:39 AM, Mikus Grinbergs <[email protected]> wrote: > Topic: What should be reportable?
Great topic. Also: what should be reportable as an ongoing class of issues, but not necssarily a repeatable bug? The lack of levels of detail beyond "leaf-level bug" makes it difficult to convert field reports into larger-scale conversations about "how should users have access to root" and "should there be man pages" and "how to determine the optimal hover-time before popping up a menu / should this be cnofigurable?" And there is no obvious way to both close a bug as 'not in current spec', 'not in immediate roadmap and hard', 'inconsistent with past implementation' and feed it into higher-level discussions about direction and audience and usability. > A step missing from that 'basic develop-test-report cycle' list: > >> 0. knowing what to expect and knowing when 'what to expect' is set in stone after a long philosophical debate, and when it is open to change via thoughtful input from testers, developers, or anyone else. Happy midwinter, SJ _______________________________________________ Testing mailing list [email protected] http://lists.laptop.org/listinfo/testing
