Re: [ClojureScript] [ANN] Orchestra 2017.07.04-1 (now supporting ClojureScript)

[Rick Moynihan]

It might be worth including a discussion about when to use this library,
and perhaps indicating that using it might not be a best-practice.

:ret and :fn specs were originally validated by instrument, but this
feature was removed because Rich et al thought it redundant, and that there
were different (and arguably better) tools for validating :ret specs, e.g.
check.

https://groups.google.com/d/msg/clojure/JU6EmjtbRiQ/WSrueFvsBQAJ

For what it's worth I understand why you might want to use this, and it's
nice to have the option if you have a legacy test suite that you want to
incorporate some specs/validation with, but if you're using it you're doing
example based testing and not the generative testing which spec seems
intended to encourage.

R.

On 8 July 2017 at 19:06, Jeaye  wrote:

> Folks,
>
> I'm happy to announce that a new version of Orchestra has been released
> this past week.
>
> # Where to find it?
> https://github.com/jeaye/orchestra
> [orchestra "2017.07.04-1"]
>
> # What is it?
> Orchestra is a Clojure(Script) library made as a drop-in replacement for
> clojure.spec.test.alpha, which provides custom instrumentation that
> validates all aspects of function specs. By default, clojure.spec will only
> instrument :args. This leaves out :ret and :fn from automatic validation;
> Orchestra checks all of them for you.
>
> # What changed since 0.3.0?
> ClojureScript support!
>
> # Any more info?
> You can read my call to arms for instrumentation here:
> https://blog.jeaye.com/2017/05/31/clojure-spec/ Also, some notes on
> porting Orchestra to ClojureScript, which extend to porting Clojure
> projects to ClojureScript in general, here: https://blog.jeaye.com/2017/
> 06/30/orchestra-cljs/
>
> # When should I use it?
> I strongly believe we can benefit from this instrumentation throughout the
> entire development cycle, so I recommend both your tests and your
> developments builds use instrumentation by default. If any functions
> misbehave, you'll know immediately and you'll have the context to find out
> why.
>
> Cheers,
> Jeaye
>
> --
> Note that posts from new members are moderated - please be patient with
> your first post.
> ---
> You received this message because you are subscribed to the Google Groups
> "ClojureScript" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojurescript+unsubscr...@googlegroups.com.
> To post to this group, send email to clojurescript@googlegroups.com.
> Visit this group at https://groups.google.com/group/clojurescript.
>

-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
"ClojureScript" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojurescript+unsubscr...@googlegroups.com.
To post to this group, send email to clojurescript@googlegroups.com.
Visit this group at https://groups.google.com/group/clojurescript.

[ClojureScript] [ANN] Orchestra 2017.07.04-1 (now supporting ClojureScript)

[Jeaye]

Folks,

I'm happy to announce that a new version of Orchestra has been released this 
past week.

# Where to find it?
https://github.com/jeaye/orchestra
[orchestra "2017.07.04-1"]

# What is it?
Orchestra is a Clojure(Script) library made as a drop-in replacement for 
clojure.spec.test.alpha, which provides custom instrumentation that validates 
all aspects of function specs. By default, clojure.spec will only instrument 
:args. This leaves out :ret and :fn from automatic validation; Orchestra checks 
all of them for you.

# What changed since 0.3.0?
ClojureScript support!

# Any more info?
You can read my call to arms for instrumentation here: 
https://blog.jeaye.com/2017/05/31/clojure-spec/ Also, some notes on porting 
Orchestra to ClojureScript, which extend to porting Clojure projects to 
ClojureScript in general, here: 
https://blog.jeaye.com/2017/06/30/orchestra-cljs/

# When should I use it?
I strongly believe we can benefit from this instrumentation throughout the 
entire development cycle, so I recommend both your tests and your developments 
builds use instrumentation by default. If any functions misbehave, you'll know 
immediately and you'll have the context to find out why.

Cheers,
Jeaye

-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
"ClojureScript" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojurescript+unsubscr...@googlegroups.com.
To post to this group, send email to clojurescript@googlegroups.com.
Visit this group at https://groups.google.com/group/clojurescript.