Very timely, the good people at Atomic Object have posted two articles about what makes code untestable, I think they're good:

This Code Is Untestable! (Part 1, for Managers) http://spin.atomicobject.com/2014/04/28/untestable-code-unit-tests/

This Code Is Untestable! (Part 2, for Developers) http://spin.atomicobject.com/2014/04/29/code-untestable-part-2-developers/

On Tue, Apr 29, 2014 at 12:47 AM, Erik Moeller erik@wikimedia.org wrote:

As a reminder, this is happening tomorrow at 12 PM PDT / 19:00 UTC tomorrow (Tuesday):

https://plus.google.com/events/cae6ng1m9o4mhdbpo10u5v05bvg

We're going to talk about various strategies for automated testing and improvements to our continuous integration infrastructure. Antoine 'hashar' Musso has offered to give an overview, roughly along these lines:

• quick overview of the infrastructure (Zuul/Jenkins, the slaves, the

myriad of jobs and how they are maintained).

• MediaWiki testing frameworks and tools (phpunit, qunit, browser

tests, beta cluster)

• current concerns in what we test, which should provide enough

materials for the open discussion part:

• lack of cross repositories tests and how to handle dependencies
• repositories that are barely tested yet critical
• mw/core tests mixing unit and integration tests
• lack of mocking
• very thin code coverage

This will be followed by an open conversation about improvement strategies. The session is scheduled to take about an hour total.

Hope to see you there :)

Erik

-- Erik Möller VP of Engineering and Product Development, Wikimedia Foundation

---

Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l