Jump to navigation

Poupou's Corner of the Web

Looking for perfect security? Try a wireless brick.
Otherwise you may find some unperfect stuff here...

Weblog

Google Code In - Week 5

Merry xmas :-) Things have slowed in the past (5th) week of Google Code In. Totals for Mono (registred melange users) are:

  • 41 tasks were completed, +1 this week
  • 0 tasks are currently claimed / worked on, -1 this week
  • 13 tasks are open and ready to be claimed by students, +1 this week
  • 19 other tasks are (still) unpublished, no change this week

Unregistred users can see all tasks from here and filter them by organization (e.g. mono).

I suspect another slow week ahead but we're still reachable on #mono-gci :-)


12/27/2010 12:09:07 | Comments | Permalink

Google Code In - Week 4

Fourth week of Google Code In is over. Totals for Mono (registred melange user) are:

  • 40 tasks were completed, +10 this week
  • 1 tasks are currently claimed / worked on, -3 this week
  • 12 tasks are open and ready to be claimed by students, no change this week
  • 19 other tasks are (still) unpublished, no change this week

Unregistred users can see all tasks from here and filter them by organization (e.g. mono).

Not sure if this is going to be a big (students vacations) or small (mentors vacations) week. In any case we're reachable on #mono-gci


12/20/2010 08:15:56 | Comments | Permalink

Google Code In / Gendarme - Special Report #2

Running Gendarme on unit tests assemblies does not seem very productive and it's not something I ever did before. However I did, more than once, some stupid mistakes that prevented all unit tests from being executed. What better solution that having a few rules specific to unit tests ?

Introducing Gendarme.Rules.NUnit.dll. A new set of speciality rules (i.e. not enabled in the default rule set) that provided a few good tasks for Google Code In students (well one student actually :-). Currently it consist of three simple rules to avoid the (well my) most common pitfalls when writing unit tests:

  • Having [Test] attributes on non-public methods, which never gets executed;
  • Missing [TestFixture] on types - this is "fixed" in NUnit 2.5 but Mono is still using (internally) the older 2.4 release;
  • Assert.* calls without a message, making them harder to find in source (even more if your stack trace is inexact)
Gendarme provides, for itself, a new target 'make check-test' to run those rules on it's own unit test (and yes a few defects were fixed ;-). It should be easy to copy/paste into your own project - even easier if you already integrated a Gendarme step into your build.

So did you ever got bite by other things while doing your unit testing ? If that can be turned into a rule then please come chat with us on #gendarme!


12/16/2010 08:37:23 | Comments | Permalink

Google Code In / Gendarme - Special Report #1

As some people might have noticed many of the Google Code In 2010 tasks being done by students for Mono are related to Gendarme.

One area, that Gendarme had not touched yet, turned out to be both easy and useful: COM interoperability rules. They are speciality rules, i.e. you need/want them or not for your project, and as such are not enabled by default. Our last survey (already two years old) showed some interest in them - actually more than some if you consider only developers using Windows (either part-time or full-time). The fact that Silverlight 4 allows COM interoperability has likely made them even more useful.

We reached a milestone last weekend when all ten (10) rules for COM interoperability (matching eleven similar FxCop rules) were completed by three students. The new rules are available in Gendarme GIT master (i.e. to be part of 2.10) in a new assembly: Gendarme.Rules.Interoperability.Com.dll.

Congratulations on all the students involved in this new assembly!


12/14/2010 17:21:23 | Comments | Permalink

Google Code In - Week 3

Third week of Google Code In is over. Less tasks (total) completed but a lot more medium and difficult tasks than the previous weeks (I should have kept statistics on points). Totals for Mono (registred melange user) are:

  • 30 tasks were completed, +9 this week
  • 4 tasks are currently claimed / worked on, no change this week
  • 12 tasks are open and ready to be claimed by students, -2 this week
  • 19 other tasks are (still) unpublished, -1 this week

Unregistred users can see all tasks from here and filter them by organization (e.g. mono).

If you have ideas for small, yet fun, tasks in the Mono eco-system then please read the rules and share them with us on #mono-gci


12/13/2010 09:23:23 | Comments | Permalink

Google Code In - Week 2

Second week of Google Code In is complete. Full stream ahead for Mono tasks! Totals so far are:

  • 21 tasks were completed, +14 this week
  • 4 tasks are currently claimed / worked on, -2 this week
  • 14 tasks are open and ready to be claimed by students, -4 this week
  • 20 other tasks are (still) unpublished, -1 this week

Don't be shy! Come and chat with us on #mono-gci


12/6/2010 08:33:56 | Comments | Permalink

The views expressed on this website/weblog are mine alone and do not necessarily reflect the views of my employer.