On Friday, December 19, 2014 6:37:14 PM UTC+1, David Nolen wrote: > On Fri, Dec 19, 2014 at 12:10 PM, Arnaud Bailly <[email protected]> > wrote: > > Well, I would like to have it in dev too... What if there is a bug or > > misused feature in the minifier/compiler? I want to catch it as quickly as > > possible. And any test I can write in the browser or using some other tool > > like selenium does not care about what the code looks like on the wire. > > As a matter of fact, when I do Haskell or Java development I use the same > > compiler flags in dev and production, because these beasts are so complex I > > do not want to get caught into believing I made a mistake where actually > > this is something related to the compiler flags. > > This is the reason why in my experience at least three environment > settings are good idea: dev, staging, production. staging looks like > production but you test here before going to production to catch bugs > that might crop up under production flags. >
Sure, that's what I do too. In the present stage of my application there is really no production (app is not live) so it boils down to 2, but you are definitely right. Thinking about it, this probably means I could: - use profiles/env for different compilation targets - have some templating in HTML (currently static but could be easily generated) to swithc between no and advanced optim, or use cljs-boot, while waiting for cljsbuild to handle it - run system-level tests against staging - run unit tests against dev (and probably staging too if possible...) This leaves me with the question: How can I unit test my stuff? Have you had experience with integrating React.js testing fwk? Thanks again for your help, Arnaud -- 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.
