On Dec 15, 2009, at 7:46 AM, Silviu Paragina wrote:
> Considering the patch I was working. I noticed that there is some
> effort
> to port the tests to rspec. Not sure how I missed that while first
> reading about tests/developing.
>
> In my patch I have modified the old test (in ./test/) to make it work.
> On the other side what is already implemented in rspec works by
> default
> (my patch only modified internal stuff), but there are 3 tests
> missing.
> Am I required to implement them in this patch. I will probably do a
> horrible job of porting to rspec, if I would try, so I'm not sure :-?
Essentially, all new tests should be in rspec, and if you're modifying
existing behaviour, if at all possible the tests for the existing
behaviour should be moved to rspec.
We can help if you have trouble with this.
--
Today at work an ethernet switch decided to take the 'N' out of NVRAM
-- Richard Letts
---------------------------------------------------------------------
Luke Kanies | http://reductivelabs.com | http://madstop.com
--
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-dev?hl=en.
