[QA] [teampractices] "Testing 101" docs from Etsy

[Dan Garry]

How about the apps, then? They're smaller, their architecture is cleaner,
and there's already some unit tests in there for one or two features that
they could use as an example.

Dan

On 29 October 2014 08:33, Chris McMahon <cmcmahon at wikimedia.org> wrote:

>
>
> On Wed, Oct 29, 2014 at 8:20 AM, Antoine Musso <hashar+wmf at free.fr> wrote:
>
>> Le 29/10/2014 12:07, Quim Gil a écrit :
>>
>> > I was wondering whether we could use Google Code-in to increase our unit
>> > testing coverage. I guess there are certain components and areas easier
>> > to to cover than others, and I guess there is DIY documentation that
>> > could be used here, but I have no idea of how feasible and useful this
>> > would be.
>>
>> Given the bad shape of Mediawiki core tests suite, I don't think Google
>> Code-in is a good fit.  I am rather suspicious toward freshmen
>> attempting to refactor our code and tests.
>
>
> As Trish Khoo of Google just remarked, "The first mistake many development
> teams seem to make, IME, is assuming testing is supposed to be easy."
>
> "...increase unit testing coverage" in our case almost certainly means
> "rewrite big chunks of Mediawiki Core from scratch".
>
> _______________________________________________
> teampractices mailing list
> teampractices at lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/teampractices
>
>


-- 
Dan Garry
Associate Product Manager, Mobile Apps
Wikimedia Foundation
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.wikimedia.org/pipermail/qa/attachments/20141029/24c5bd3d/attachment.html>