On Wed, Jan 28, 2009 at 11:18 AM, Frantisek Sodomka wrote:
>
> Shawn, I keep wondering where is the best place to put tests for bug fixes.
> One way would be to create a separate file (bugs.clj) and put all these
> tests there. Another way is to include these tests into their respective
> categori
Hello Steve,
I attached file predicates.patch for type and number predicates. Let me
know, if this is an acceptable patch (I haven't worked with them before). We
can then create an issue for Clojure-contrib if necessary.
Shawn, I keep wondering where is the best place to put tests for bug fixes.
O
On Jan 26, 2009, at 7:43 PM, Shawn Hoover wrote:
I have a few tests in the works and am lacking commit access as
well. Should test contributions follow the procedure of group
discussion, then file an issue, then post a patch? If so, what would
you like to know about the patch(es)?
I cons
On Sun, Jan 25, 2009 at 6:51 PM, Frantisek Sodomka wrote:
> I have some tests ready for test_clojure. I asked Rich for SVN access
> rights. There is gonna be more tests soon :-)
>
> Frantisek
>
Contrib Stewards,
I have a few tests in the works and am lacking commit access as well. Should
test co
I have some tests ready for test_clojure. I asked Rich for SVN access
rights. There is gonna be more tests soon :-)
Frantisek
On Sun, Jan 25, 2009 at 8:55 PM, Stuart Halloway
wrote:
>
> In SVN 412 I have made the following changes to contrib:
>
> * a test_contrib.clj file which does for contrib
In SVN 412 I have made the following changes to contrib:
* a test_contrib.clj file which does for contrib what test_clojure.clj
does for clojure
* a test_clojure task in build.xml
* a test_contrib task in build.xml
* a test task to aggregate all test tasks
This is *very* minimal, but I wanted
