Hi everyone, Ivan and I have taken the interesting approach to collaboration by each working on our own subtly different mock objects implementation, communicating regularly and stealing each other's ideas where necessary. I released my crude attempt yesterday in case anyone wants to play around with it:
gem install markryall-orangutan (from gems.github.com) or gem install orangutan (from rubyforge) At this stage, you can only create stubs that implement a clr interface (as well as pure ruby stubs) and then tell them how to behave (return values, raise errors and yield values). I'll add subclassing of clr classes and a nicer DSL for checking what actually happened. See http://github.com/markryall/orangutan/tree/master and http://github.com/casualjim/caricature/tree/master Before long, we'll combine our efforts into one super mock object library that will mock objects like they've never been mocked before. Mark. On Fri, May 8, 2009 at 5:00 AM, Shri Borde <[email protected]> wrote: > This “newsletter” is just part of the contents of > http://wiki.github.com/ironruby/ironruby/contributing for your reading > convenience, filtered down to projects with an updated status since last > time. A number of the projects have made good progress since a few weeks > ago. Please take a look at the projects that interest you, give feedback to > the project owners for bugs or features you care about, and discuss ways of > being involved if you are interested. > > > > Regards, > > Shri > > > Mixing Ruby mocking with .NET mocking frameworks > > Mark Ryall, Ivan Porto Carrero > > Investigated Moq and NMock and found that they were not a good match. A > project called Caricature <http://github.com/casualjim/caricature/> has > been started to implement mocking directly in IronRuby > Hpricot <http://github.com/nrk/ironruby-hpricot/> > > Daniele Alessandri > > Status: the master branch (compatible with Hpricot 0.6.164) and the > 0.7_experimental branch (compatible with Hpricot 0.8.1) in the repository > both pass all the tests of the original Hpricot test suite, what is left is > a major clean up and some refinements to the code. > Json <http://github.com/nrk/ironruby-json> > > Daniele Alessandri > > Status: it somewhat works but needs to be tested, so bugs are expected at > this stage. A rewriting of the original definition file for Ragel is planned > to improve the C# code of the ParserEngine class which currently is not so > object oriented. > IRDb <http://github.com/rvernagus/irdb> > > Project State: Alpha > > Developer(s): Ray Vernagus <http://github.com/rvernagus> > > A Ruby wrapper on top of the .NET Data Provider > Model.<http://msdn.microsoft.com/en-us/library/a6cd7c08.aspx>This wrapper > will become the basis for an ActiveRecord adapter giving > IronRuby developers the ability to use the ActiveRecord gem with their > choice of database. > Rails <http://rubyonrails.org> > > Jimmy Schementi, Ray Vernagus > > Details status about setting up Rails, running the unit tests, etc, is at > http://www.ironruby.net/Documentation/Rails. > OpenSSL <http://www.ruby-doc.org/stdlib/libdoc/openssl/rdoc/index.html> > > Jirapong Nanta > > Status: There are about 330 methods for OpenSSL library. Less than ten > RubySpec <http://wiki.github.com/ironruby/ironruby/rubyspec> are > available. The focus of the project will be implementation the functionality > that is needed for RubyGems and Rails scenarios. e.g. > OpenSSL::X509::Certificate. Current results of running mspec ci > library\openssl can be found here <http://gist.github.com/100649>. > > Work process: > > * Checkout ruby 1.8 source code > > * review OpenSsl implementation in C (ruby_1_8\ext\openssl) > > * review OpenSsl usage in RubyGems (e.g. rubygems\lib\rubygems\gem_openssl.rb) > > * write RubySpec > > * implement a wrapper to System.Security.Cryptography namespaces > > * Refactor < - > Push > > Some useful documentations can be found at > http://technorama.net/~oss/ruby/openssl/doc/ > Porting SOAP Weather > Widget<http://silverlight.net/community/gallerydetail.aspx?cat=sl2> > > Shay Friedman > > Status – project was created, started porting the Silverlight code. > RubyGems > > Shri Borde, Jirapong Nanta > > We have reduced the number of failueres from 200+ down to about 20. The > current results are here <http://gist.github.com/92738>. The tests can now > be run from a Dev.bat > <http://wiki.github.com/ironruby/ironruby/devbat>environment, and will soon > be part of continuous integration. So this > project is mostly wrapping up (successfully). > Cucumber > > Chamini Gallage > > Blocking IronRuby bug has been fixed. Need to try again with a newer > IronRuby version > > _______________________________________________ > Ironruby-core mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/ironruby-core > >
_______________________________________________ Ironruby-core mailing list [email protected] http://rubyforge.org/mailman/listinfo/ironruby-core
