I’ve decided to try something a little different. Instead of getting a word document passed around to look at and review, I’ve decided to put my .NET interop test plan on our public Ironruby wiki to get comments from the team and the community. It’s not perfect, it’s what I’d normally call 1^st draft, but this is how I’m going to do this one.

You can find it here: http://ironruby.net/.NET_Testing_plans

We’re going to have to have a discussion about what .NET interop means for IronRuby, and what cases are going to work, and what cases aren’t. I’d love to have this page be a starting point for that discussion. Turn the bullet points into links, and we can decide what the case means, how it should look, and how it should work.

The way it works now is scenarios and cases. Each scenario describes a .NET object or type. Each case is how to use that object or type. It’s essentially a matrix in bullet form, scenarios are rows, cases are columns, or vice versa. This leads to a lot of test cases, which is another area I could use help. I would love if people would write tests that correspond to these cases. I’ll be writing them too.

I’ll be writing them with the MSpec framework. I’ll be getting a folder structure set up in the repo at $SVN_ROOT/trunk/tests/ironruby/interop. The structure will be based on the sections of this page. I’ll try to write up some pages and links on MSpec for people who aren’t familiar with it.

As you read this, feel free to make changes, sign up for an account if needed. If you have questions about what I meant, feel free to ask. I’ll do my best to explain. This is as much an experiment for me as it may be for you.

My Blog

This is my new blog where I’ll be posting all my thoughts about testing the IronRuby implementation. I’ll also be posting thoughts on testing, language design, language interop, and applying testing theory to a language implementation. 

Me

I’m a new hire at Microsoft, I’ve been working there since April. I’ll also try to post thoughts on working there too. My prior experience with Ruby includes playing with it since mid-2006, and Ruby on Rails programming for Genetree, Inc. I’m not an expert to the level of _why, but I know my way around. At Genetree, we did TDD/BDD using RSpec, which is where I learned about testing. 

I’m a fan of Open Source software, and I’m proud to be part of one of the the first Open Source projects at Microsoft. In the past I’ve made contributions to Rails and RSpec (under the username parcelbrat), and I intend to get involved with them again once I get my head above water at Lake Microsoft ;). 

More Blog Stuffs

I look forward to having conversations with you, and have kept commenting open for that reason. First time moderation is required, but it’s open after that. If you feel the need to contact me privately, you can reach me at jdevilleATmicrosoftDOTcom.

UPDATE: Changed heading sizes to not look like post titles