Speed up your development cycle using example. Here's the process:
1. Write your test code inline with your functions.
2. Test the output of your functions in the REPL as you code.
3. Generate unit tests when you're satisfied with the behavior of your
functions.
See
Hi David,
How does this integrate prerequisites? Even if my fn is pure, I still mock
calls made within.
On Mon, Jun 8, 2015 at 5:33 PM, David Sargeant da...@dsargeant.com wrote:
Speed up your development cycle using example. Here's the process:
1. Write your test code inline with your
I'm not totally sure why you would need to use `provided` with pure
functions, but that is definitely not in scope for this project. example
isn't meant to replace all cases where you would write tests. It's designed
to streamline the creation of a certain class of tests that come with a lot
If I need something more complicated in terms of testing my functions I
usually create a file dev/examples.clj and add dev to the source-paths in
my project's dev profile. I would require the namespace with my functions
and put the examples in dev/examples.clj. The rest of the process is the
Got it. Thanks!
On Mon, Jun 8, 2015 at 6:14 PM, David Sargeant da...@dsargeant.com wrote:
I'm not totally sure why you would need to use `provided` with pure
functions, but that is definitely not in scope for this project. example
isn't meant to replace all cases where you would write tests.
I meant (provided), (against-background), etc.
On Mon, Jun 8, 2015 at 6:02 PM, David Sargeant da...@dsargeant.com wrote:
If I need something more complicated in terms of testing my functions I
usually create a file dev/examples.clj and add dev to the source-paths in
my project's dev profile.
