[Sugar-devel] Call for testing

Wade Brainerd wadetb at gmail.com
Wed Jan 27 07:20:56 EST 2010


On Sun, Jan 17, 2010 at 6:36 PM, Christian Marc Schmidt
<christianmarc at gmail.com> wrote:
>
> On Jan 17, 2010, at 6:14 PM, Wade Brainerd <wadetb at gmail.com> wrote:
>
>> On Sun, Jan 17, 2010 at 6:01 PM, Simon Schampijer <simon at schampijer.de>
>> wrote:
>>>
>>> Great, I will think about the test protocol, too. And, i will work on a
>>> patch that helps us to easily switch between the two scenarios for
>>> testing.
>>>
>>> Thanks for all those thoughts - I think we are on the right track,
>>
>> IMO, automated evaluation would also be useful.  For example, logging
>> how often various menu items are clicked.  Just adding a log print to
>> each UI control would be sufficient; we can harvest and analyze the
>> logs later.
>>
>> For example, it might be useful to know how many new activities are
>> started before/after the change.  If it goes up by a little, we're
>> probably okay.  But if it goes up drastically, it might be a problem.
>> I don't think we need to get into deep statistical analysis, but it
>> might be useful to have the data available.
>>
>> -Wade
>
> That is a very good idea. How long would it take to implement?

It would not be hard to implement; I'll try and make a test patch
which adds the logging soon.

Then we would use the Report a Problem CP (or the Feedback activity,
if that becomes real) to harvest the logs.

-Wade


More information about the Sugar-devel mailing list