Got it. Thanks. 

I voted for the jira issue.

On Tue, Dec 30, 2014 at 3:49 PM, David Nolen <[email protected]>
wrote:

> This is a tooling issue more than anything, you need to recompile the
> namespace with the `run-tests` expression.
> However, there is utility to a :recompile-dependents flag, and we
> already have a JIRA ticket for this. When it is implemented it will
> trigger all dependent namespaces to recompile.
> David
> On Tue, Dec 30, 2014 at 4:27 AM, Yehonathan Sharvit <[email protected]> wrote:
>> I have played with the tutorial provided here: 
>> http://keeds.github.io/clojurescript/2014/12/19/cljs-test.html
>>
>> It seems that new tests inside an existing namespace are not run when using 
>> lein cljsbuild auto test.
>>
>> Is it a bug in cljs.test?
>>
>>
>>
>> On Wednesday, 24 December 2014 20:40:03 UTC+2, David Nolen  wrote:
>>> Time between releases are pretty variable though they tend to be
>>> pretty frequent around new features like cljs.test as issues need to
>>> be ironed out.
>>>
>>> I'll probably cut another release on Friday.
>>>
>>> David
>>>
>>> On Wed, Dec 24, 2014 at 1:32 PM, Yehonathan Sharvit <[email protected]> 
>>> wrote:
>>> > Great news David!
>>> >
>>> > What is the usual delay (in days) between commit to the master and 
>>> > release?
>>> >
>>> > On Wednesday, 24 December 2014 20:18:39 UTC+2, David Nolen  wrote:
>>> >> The `are` macro isn't in a current release, however it's in master and
>>> >> will appear in the next one. Otherwise Russell's assessment is
>>> >> correct.
>>> >>
>>> >> David
>>> >>
>>> >> On Wed, Dec 24, 2014 at 1:13 PM, Yehonathan Sharvit <[email protected]> 
>>> >> wrote:
>>> >> > What about the 'are' macro?
>>> >> >
>>> >> >
>>> >> >
>>> >> > On Wed, Dec 24, 2014 at 7:38 PM, Russell Mull <[email protected]>
>>> >> > wrote:
>>> >> >>
>>> >> >> Things that aren't in cljs.test:
>>> >> >>
>>> >> >> with-test
>>> >> >> run-tests can take a custom environment parameter. Things that 
>>> >> >> required
>>> >> >> rebinding a var in clj.test are configured with an entry in the 
>>> >> >> environment.
>>> >> >>
>>> >> >> :reporter, instead of rebinding the report function
>>> >> >> :testing-contexts instead of *testing-contexts*
>>> >> >> :testing-vars instead of *testing-vars*
>>> >> >>
>>> >> >> And that's it. It looks like a nearly complete port.
>>> >> >>
>>> >> >> - Russell
>>> >> >>
>>> >> >>
>>> >> >>
>>> >> >>
>>> >> >> On Tuesday, December 23, 2014 1:59:45 PM UTC-8, Yehonathan Sharvit 
>>> >> >> wrote:
>>> >> >>>
>>> >> >>> What is the gap between clojure.test and cljs.test?
>>> >> >>>
>>> >> >>> For exmaple: is the `are` macro implemented in cljs.test?
>>> >> >>>
>>> >> >>> On Wednesday, 17 December 2014 23:54:09 UTC+2, David Nolen  wrote:
>>> >> >>> > ClojureScript, the Clojure compiler that emits JavaScript source 
>>> >> >>> > code.
>>> >> >>> >
>>> >> >>> > README and source code: https://github.com/clojure/clojurescript
>>> >> >>> >
>>> >> >>> > New release version: 0.0-2496
>>> >> >>> >
>>> >> >>> > Leiningen dependency information:
>>> >> >>> >
>>> >> >>> >     [org.clojure/clojurescript "0.0-2496"]
>>> >> >>> >
>>> >> >>> > The big change in this release is a port of the clojure.test 
>>> >> >>> > namespace
>>> >> >>> > - cljs.test.
>>> >> >>> > It is largely compatible with clojure.test and implements enough
>>> >> >>> > functionality such
>>> >> >>> > that we could port all of the existing tests to it. It's also
>>> >> >>> > featureful enough
>>> >> >>> > to support a ClojureScript port of test.check that is underway.
>>> >> >>> > cljs.test is compatible
>>> >> >>> > with all of the optimization settings provided by the compiler
>>> >> >>> > including :none.
>>> >> >>> >
>>> >> >>> > Still cljs.test may not satisfy all the patterns that people have 
>>> >> >>> > come
>>> >> >>> > to expect
>>> >> >>> > from clojure.test so feedback (and enhancement/fix patches) is very
>>> >> >>> > welcome.
>>> >> >>> >
>>> >> >>> > On the way we implemented changes to the compiler in order to make
>>> >> >>> > custom testing
>>> >> >>> > frameworks simpler to implement - this includes compiler support 
>>> >> >>> > for
>>> >> >>> > :test metadata as well
>>> >> >>> > as introducing static vars.
>>> >> >>> >
>>> >> >>> > ClojureScript does not have vars, however there are var patterns 
>>> >> >>> > that
>>> >> >>> > are largely
>>> >> >>> > static in nature and useful for metaprogramming and REPL 
>>> >> >>> > interactions.
>>> >> >>> > Towards
>>> >> >>> > this end we've implemented the `var` special form and introduced 
>>> >> >>> > very
>>> >> >>> > restricted
>>> >> >>> > functionality - metadata is the primary use case.
>>> >> >>> >
>>> >> >>> > (defn foo [])
>>> >> >>> > (meta #'foo) ;; will return the expected metadata
>>> >> >>> >
>>> >> >>> > cljs.test is implemented on top of this functionality as well as a 
>>> >> >>> > new
>>> >> >>> > namespace
>>> >> >>> > cljs.analyzer.api which I think macro writers will find quite 
>>> >> >>> > useful.
>>> >> >>> >
>>> >> >>> > Also there's a doc macro now in the cljs.repl namespace that works 
>>> >> >>> > as
>>> >> >>> > expected.
>>> >> >>> > Patches welcome to bring all the useful bits of clojure.repl into
>>> >> >>> > cljs.repl.
>>> >> >>> >
>>> >> >>> > ## 0.0-2496
>>> >> >>> >
>>> >> >>> > ### Enhancements
>>> >> >>> > * cljs.test added, mirrors clojure.test
>>> >> >>> > * New cljs.analyzer.api namespace for easier access to analysis 
>>> >> >>> > info
>>> >> >>> > from macros
>>> >> >>> > * New cljs.analyzer.api namespace for easier access to analysis 
>>> >> >>> > info
>>> >> >>> > from macros
>>> >> >>> > * Support :test metadata on vars
>>> >> >>> > * Support static vars
>>> >> >>> > * cljs.source-map for client side source mapping
>>> >> >>> > * expose ClojureScript :warnings build option
>>> >> >>> > * CLJS-909: Add stable api for consumers of compiler data.
>>> >> >>> >
>>> >> >>> > ### Changes
>>> >> >>> > * convert all ClojureScript tests to cljs.test
>>> >> >>> > * add volatile! from Clojure 1.7
>>> >> >>> > * stateful transducers use volatile!
>>> >> >>> > * added `js-debugger` macro, compiles to "debugger;"
>>> >> >>> > * CLJS-892: Improve performance of compare-symbols/compare-keywords
>>> >> >>> > * CLJS-696: remove arguments usage from defrecord constructor
>>> >> >>> > * unroll `partial`, copy & pasted from Clojure core.clj
>>> >> >>> > * optimize clojure.string/join
>>> >> >>> >
>>> >> >>> > ### Fixes
>>> >> >>> > * fix `cljs.nodejs/enable-util-print!`, incorrectly monkey patched
>>> >> >>> > `cjls.core/string-print` instead of setting `cljs.core/*print-fn*`
>>> >> >>> > * cljs.reader bug, '/ incorrectly read
>>> >> >>> > * avoid emitting the same goog.require
>>> >> >>>
>>> >> >> --
>>> >> >> Note that posts from new members are moderated - please be patient 
>>> >> >> with
>>> >> >> your first post.
>>> >> >> ---
>>> >> >> You received this message because you are subscribed to a topic in the
>>> >> >> Google Groups "ClojureScript" group.
>>> >> >> To unsubscribe from this topic, visit
>>> >> >> https://groups.google.com/d/topic/clojurescript/gnCl0CySSk8/unsubscribe.
>>> >> >> To unsubscribe from this group and all its topics, send an email to
>>> >> >> [email protected].
>>> >> >> To post to this group, send email to [email protected].
>>> >> >> Visit this group at http://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 [email protected].
>>> >> > To post to this group, send email to [email protected].
>>> >> > Visit this group at http://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 [email protected].
>>> > To post to this group, send email to [email protected].
>>> > Visit this group at http://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 [email protected].
>> To post to this group, send email to [email protected].
>> Visit this group at http://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 a topic in the Google 
> Groups "ClojureScript" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/clojurescript/gnCl0CySSk8/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> [email protected].
> To post to this group, send email to [email protected].
> Visit this group at http://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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/clojurescript.

Reply via email to