Le 15/01/2015 18:31, Legoktm a écrit :
On 01/14/2015 04:57 PM, James Douglas wrote:
I'd love to hear your thoughts and learn about your related experiences.
What are your favorite code coverage tools and services?
PHPUnit has a useful code coverage tool and there are reports running
for
On 01/14/2015 04:57 PM, James Douglas wrote:
I'd love to hear your thoughts and learn about your related experiences.
What are your favorite code coverage tools and services?
PHPUnit has a useful code coverage tool and there are reports running
for core[1] and some extensions[2]. In my
I'd love to use coveralls for the iOS app! I've thought it (and Travis)
looked promising before, put seem especially relevant for mediawiki
projects which are all OSS.
One other JS testing lib you guys should check out is JSVerify
http://jsverify.github.io/, which is a port of Haskell's
+1 for property-based testing. JSVerify's Haskell-like syntax makes it
super easy to conjure up arbitrary generators.
On Thu, Jan 15, 2015 at 7:44 AM, Brian Gerstle bgers...@wikimedia.org
wrote:
I'd love to use coveralls for the iOS app! I've thought it (and Travis)
looked promising before,
Howdy all,
Recently we've been playing with tracking our code coverage in Services
projects, and so far it's been pretty interesting.
We've learned about where the gaps are in our testing (which has even
revealed holes in our understanding of our own specifications and use
cases), and had fun
On 01/14/2015 06:57 PM, James Douglas wrote:
Howdy all,
Recently we've been playing with tracking our code coverage in Services
projects, and so far it's been pretty interesting.
Based on your coverage work for restbase, we added code coverage using
the same nodejs tools (instanbul) and
