<div class="gmail_quote">On Fri, Feb 26, 2010 at 10:27 PM, Tom Parker <span dir="ltr"><<a href="mailto:tom@carrott.org">tom@carrott.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Thu, 2010-02-25 at 07:56 +1300, Tim McNamara wrote:<br>
<br>
<br>
> I would love there to be one webpage for test<br>
> requests that has some<br>
> visual indicator of how many people testing it<br>
> and how close to<br>
> finished testing it is, with a big tick next<br>
> to it when it has been<br>
> tested thoroughly. </div></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Something as "simple" as a tracker would work. If you want something<br>
tested, raise a ticket. Developers can look at the ticket to see what<br>
the status of your test request is. Testers can look at the list of open<br>
tickets to see what is ready for testing. Every request has a date and a<br>
log of what has been done. This is how the test groups work in the<br>
software development houses I've worked with.<br></blockquote><div><br></div><div><div class="gmail_quote"><div>This is worth investigating. Properly written test cases & test requests will solve these issues. What do we test today? What has been taken up by other groups when that email came through to x, y, z list? What methodology do Activity developers want used?</div>
<div><br></div><div>Bug/ticket triaging becomes significant.. because these reports are not bugs. </div><div><br></div><div>I sense this may place unnecessary burden on developers over time. First of all, it creates noise in the tracker. Secondly, devs will need to create a new ticket for the next version of whatever component, but the test cases remain the same. They just want they tests replicated for a new update. At every release of a new activity, what set of functionality should be tested to ensure consistency between releases?</div>
<div><br></div><div>I like the fact that we don't need much more infrastructure, but don't know how practical things will be in the medium term.</div><div><br></div><div>-Tim.</div></div></div></div>